Contents

Configuration

Configuration is handled by collections of named parameters. All parameters start with a default value which is over-ridden by the contents of the configuration file (most often named "LookingGlass.json", then user specific saved parameters and then command line parameters.

You can see a sampling of all the parameters with explanations on the default parameters page.

LookingGlass.json

Modules.json

LookingGlass reads the file Modules.json before LookingGlass.json and you can consider the two files concatenated together. The original design was to have all the module definitions in this file since the module linkage is required and shouldn't be confused with the optional parameter overrides that appear in LookingGlass.json. This might happen yet.

The modules are specified as a JSON array of module specifications. Modules are not dynamically searched for but are loaded if specified in the modules configuration section.

For each module, the following must be specified:

Assembly

the name of the assembly file (usually a dll to search for the interface

Interface

the name of the interface to find. The interface must also include the IModule interface

Name

a name for this module. Other modules find this module by this name. In theory, one could have multiple viewers looking into the world and this would be done by specifying the viewer multiple times but with different names.