Starmapper Site : UnifiedConfigurationModel

HomePage :: Categories :: PageIndex :: RecentChanges :: RecentlyCommented :: Login

Revision [100]

Last edited on 2007-09-20 12:33:18 by KrzysztofSobolewski [Add a link to another page with settings.]
Additions:
The list of config values/paths recognized by Starmapper is documented in javadocs for [[http://starmapper.sourceforge.net/api/starmapper3/trunk/jezuch/utils/starmapper3/config/Config.html Config]] class (look for public static fields named ""SET_*""). The list, along with additional settings from various components, is repeated on [[AvailableSettings]] page.
Deletions:
The list of config values/paths recognized by Starmapper is documented in javadocs for [[http://starmapper.sourceforge.net/api/starmapper3/trunk/jezuch/utils/starmapper3/config/Config.html Config]] class (look for public static fields named ""SET_*"").


Revision [99]

Edited on 2007-09-20 12:23:58 by KrzysztofSobolewski [Add a reference to the list of settings in Config javadocs]
Additions:
===Config values===
The list of config values/paths recognized by Starmapper is documented in javadocs for [[http://starmapper.sourceforge.net/api/starmapper3/trunk/jezuch/utils/starmapper3/config/Config.html Config]] class (look for public static fields named ""SET_*"").


Revision [87]

Edited on 2007-08-08 14:38:18 by KrzysztofSobolewski [Mention programmatic access to Config]
Additions:
The properties form a hierarchy and each property is accessible via a //path//, for example ""regions.reg1.name"" - the path is usually given in dotted notation, where the leftmost part is the topmost (most general) in the hierarchy, but that's purely for human convenience; see [[http://starmapper.sourceforge.net/api/starmapper3/trunk/jezuch/utils/starmapper3/config/Config.html javadocs for Config]] class for details how it's handled internally - the only thing you need to know is that there's a hierarchy, unless you want programmatic access to the configuration API.
Deletions:
The properties form a hierarchy and each property is accessible via a //path//, for example ""regions.reg1.name"" - the path is usually given in dotted notation, where the leftmost part is the topmost (most general) in the hierarchy, but that's purely for human convenience; see [[http://starmapper.sourceforge.net/api/starmapper3/trunk/jezuch/utils/starmapper3/config/Config.html javadocs for Config]] class for details how it's handled internally - the only thing you need to know is that there's a hierarchy.


Revision [86]

The oldest known version of this page was created on 2007-08-08 14:36:36 by KrzysztofSobolewski [Added UnifiedConfigurationModel page]
Valid XHTML 1.0 Transitional :: Valid CSS :: Powered by WikkaWiki
SourceForge.net Logo
Page was generated in 0.1210 seconds