Display an external scene as it was defined at this point of the scene graph.
At M4M creation time, each item that is a path to a local and valid VRML file
triggers the compilation and inclusion of the resulting M4M file. The process is
recursive.
If the child scene, through the use of an Anchor node, changed itself, the name
of this new scene (including empty string) is set as first item of the url field.
In addition, Inline gives you the opportunity to select a language pack for the scene that is inlined. The underlying internationalisation mechanism is quite simple. When you design your scene (thus resulting into an M4M file), you can specify special strings for will act as "localized" string. It mostly consists in a token enclosed by special chars. This token will be used at runtime to check a litteral definition in language pack. For instance you will use "@[hello:]" in a VRML file and you will be able to specify that this should be replaced at runtime by "bonjour" if the mobile interface is in french. If you want to reuse this localized string, just omit the colon (":") like that "@[hello]". When compiling the vrml files, all the localize strings are identified and stored in a file named "default.lang" and stored at the root level of your inlined scene. Do not edit this file as it is automatically generated but rather duplicate it and fill it in with your translation. This files consists in a list of all tokens (e.g. "hello:"). In your duplicate, just add the translation after the colon like this "hello:bonjour tout le monde". You will probably name this duplicate file using the language it represents but always keep the ".lang" extension. To use your own language pack, specify them in the field named "languages". Each further compilation process will keep track of the synchronization between your files and default.lang so you will always have up to date language packs.
You can use this mechanism to localize images but they must be all referenced in the url field of an ImageTexture.
MFString url [] :
Only the first item is loaded to be displayed at runtime.
Other items are checked to search for scenes to compile and include at compile time.
The first item of the url field can contain several different values:
Warning:
Only use M4M files in URL.
Don't use WRL files ( cause problems during the
final M4M file creation).
MFString languages [] :
Couples of country code and language files to use. The lang file must be a copy of the generated default.lang. If the entires do not match, warnings are issued.
For Instance, to specify that you want to use french.lang when for a french phone and english.lang for an english phone
MFString use [] :
Give a full control over which language is used. The first string will probably be always "auto" to specify that you want to match the phone settings with one of the language packs defined. A second string gives the default language to use if the phone has been set in an unknown language (at least one that does not appear in "languages")