How to use

Contents

• Contents
• Starting configuration
  • Config file
  • Command line arguments
• Populate objects
• Object hierarchy

Starting configuration

Config file

In the "OGREE 3D_Data" folder, we can find "config.json".

Name	Value	Comment
verbose	true or false
fullscreen	true or false
textures	name:path	can be a local file or an url
db_url	url
db_token	id token for api

Command line arguments

Each config file parameter can be overrided with a command line argument

--verbose [true|false]
--fullscreen [true|false]
--serverUrl [url]
--serverToken [token]

You can also start the client with an .ocli file:

--file [path to ocli file to load]

Populate objects

To populate object, you can either load a .ocli file with CLI commands written in it or type them directly on the build-in CLI.
Details about the CLI langage: https://github.com/ditrit/OGREE-3D/wiki/CLI-langage.

When you load a .ocli file, all commands in this file will be put at the end of the current file. If you want to modify an object, you should create and modify it in the same .ocli file.

Object hierarchy

We have to respect this object hierarchy in order to populate objects.

Tenant
 |_ Site
     |_ Building
         |_ Room
             |_Rack
             |  |_ Device
             |  |   |_ Device
             |  |   |   |_ Device
             |  |   |   |_ Device
             |  |   |_ ...
             |  |_ Device
             |  |_ Group
             |  |_ ...
             |_ ...
             |_ Group                     \
             |_ Corridor                  | 
             |_ PowerPanel                |
             |_ Separator                 | NO CHILDREN
             |_ AirConditioningSystem     |
             |_ Cabinet                   /