Content loading order

1. Loading common preferences

Each module in group tries to load common preferences after loading itself.

The common preferences file must be named like <groupName>_prefs.xml. In example, modules are included in group with name virtualTour1, then they will try to load file virtualTour1_prefs.xml.

If you want to use common preferences, this file must reside in the same directory as modules *.swf file.

If loading of the file is succesful and it contains valid data, preferences applying. Every parameter of common preferences is applicable to all kinds of modules.

2. Loading specific preferences

Regardless of common preferences loading result, after that every module tries to load its own specific preferences from file <filesLocation>/<containerID>_prefs.xml.

The value of <filesLocation> can be defined in common preferences. If it is not defined, specific preferences file (and all other stuff for this group) will be searched in same directory as modules *.swf file. This file must be named like <containerID>_prefs.xml. For example, myMapModule_prefs.xml for one of modules in example.

If loading of the file is succesful and file contains valid data, preferences applying.

3. Loading content

Content for any module must be described in XML data file. To load content module must load data file, and loading data file immediately followed by loading content files defined in it. All data files must reside within <filesLocation>, if this parameter defined in preferences.

If you want module to load any content on startup, you have to set value of <initialLoadData> in preferences. The value must be a name of data file, for example myCoolPanorama.xml. This file will be loaded immediately after loading preferences, then content loading will start. If <initialLoadData> not defined, module will remain empty until command to load data will be received.