"Extensions" container
(import explanatory text from the TCCCG) |
|||
| Line 1: | Line 1: | ||
| − | + | The [["extensions" container]] is a top-level [[config.txt file]] entry available to any Asset which derives from [[KIND TrainzBaseSpec]] (in short, all Assets.) This container is intended to allow third-party developers to introduce custom Asset-keyed data which may be processed by custom scripts. | |
| − | + | ||
| − | + | The extensions container is a list of custom tags or subcontainers with a specific naming convention. | |
| − | + | ||
| − | + | ||
| − | Each tag in the extensions container may be either a single value, or a subcontainer. If a subcontainer is used, the contents of the subcontainer should be specified in the | + | |
| − | No restrictions are placed by | + | ==Supported Tags== |
| + | |||
| + | The naming of top-level tags within the [["extensions" container]] is important. Tag names should be meaningful and must end with a hyphen followed by the [[UserID]] of the content creator who is introducing the extension. This content creator is solely responsible for determining any rules and restrictions which apply to the tag or subcontainer, and should ideally make an effort to provide this information to other creators via this wiki. While content creators are permitted to make use of each other's extension formats, it is not permissible for a creator to introduce a new extension (or change the meaning of an extension) which exists in a namespace belonging to another content creator. | ||
| + | |||
| + | Each tag in the extensions container may be either a single value, or a subcontainer. If a subcontainer is used, the contents of the subcontainer should be specified in the extension documentation. No restrictions are placed by N3V on the values within a specific extension. | ||
| + | |||
| + | ==Validation== | ||
| + | |||
| + | At the current time, the contents of the [["extensions" container]] is not validated. It is expected that future versions of Trainz and the [[Download Station]] will perform validation of the extensions container according to the rules described on this page. Furthermore, it is feasible that N3V will formally adopt specific extensions which have entered common use. In this scenario, N3V may choose to introduce asset validation to the extension creator's formal specification or, where such specification is not available, to a formal specification written by N3V derived from the common usage. | ||
| + | |||
| + | =="extensions" container Example== | ||
| + | |||
| + | extensions | ||
| + | { | ||
| + | TBD | ||
| + | } | ||
| + | |||
| + | [[Category:Config Container]] | ||
Revision as of 00:42, 18 October 2010
The "extensions" container is a top-level config.txt file entry available to any Asset which derives from KIND TrainzBaseSpec (in short, all Assets.) This container is intended to allow third-party developers to introduce custom Asset-keyed data which may be processed by custom scripts.
The extensions container is a list of custom tags or subcontainers with a specific naming convention.
Supported Tags
The naming of top-level tags within the "extensions" container is important. Tag names should be meaningful and must end with a hyphen followed by the UserID of the content creator who is introducing the extension. This content creator is solely responsible for determining any rules and restrictions which apply to the tag or subcontainer, and should ideally make an effort to provide this information to other creators via this wiki. While content creators are permitted to make use of each other's extension formats, it is not permissible for a creator to introduce a new extension (or change the meaning of an extension) which exists in a namespace belonging to another content creator.
Each tag in the extensions container may be either a single value, or a subcontainer. If a subcontainer is used, the contents of the subcontainer should be specified in the extension documentation. No restrictions are placed by N3V on the values within a specific extension.
Validation
At the current time, the contents of the "extensions" container is not validated. It is expected that future versions of Trainz and the Download Station will perform validation of the extensions container according to the rules described on this page. Furthermore, it is feasible that N3V will formally adopt specific extensions which have entered common use. In this scenario, N3V may choose to introduce asset validation to the extension creator's formal specification or, where such specification is not available, to a formal specification written by N3V derived from the common usage.
"extensions" container Example
extensions
{
TBD
}
