NeptuneLabs FSI Viewer JS User Manual page 18

2. You can store image specific parameters in additional *.xml files in
WEBAPPS/fsi/viewer/config/
Parameters specified in multiple ways – for example in the default configuration
and by custom configuration files– will be evaluated in the following way:
The list below shows the hierarchy resulting from the sequential
evaluation of the different configuration methods:
Configuration Hierarchy
Choosing the adequate Configuration Method
So far you learned that FSI Viewer JS can be configured by any
combination of:
These configuration options are not only alternate methods. Combining
these methods offers the possibility to provide configuration parameters
as easily as possible and as dynamically as required. The following
considerations might be helpful when deciding which method to choose for
a certain parameter.
Default Configuration
You can easily change global parameters that apply to all FSI Viewer instances
by editing a single file. This is therefore the recommended configuration
method for:
General configuration options like:
Skin
l
Language
l
MenuAlign, AnimationSpeed and alike
l
Configuration Files
Separate configuration files should be used for parameters specific to a group
of images or a specific way to display images. You might for example want to
setup individual configuration files for different types of FSI Viewer JSinstances,
like "small_no_interface. xml", "large_with_hotspots.xml" as an example.
NeptuneLabs - FSI Viewer
Parameters defined in configuration files override parameters
l
defined in the default configuration file "_default.xml".
1. Configuration file (*.xml)
2. Default configuration file (_default.xml)
The default configuration file (_default.xml)
l
Additional configuration files (*.xml)
l
2 FSI Viewer JS
18