 MelvMay-GG
|
61544fec27
- Completely rewritten the Taml visitor/parser set-up this morning. Now TAML can perform parsing requests for visitors for potentially any format i.e. you can write a visitor without having knowledge of the format being read. Only an XML parser is currently present but I'm now writing JSON and BINARY parsers. With a JSON and BINARY parser in place you will be able to define things like asset-definitions and module-definitions in any TAML format (any that has a parser).
|
12 years ago |
|
MelvMay-GG
|
1d007c26a4
- TAML now supports writing and reading JSON. By default it will use a schema that is strictly compatible with JSON RFC4627 (specifically the part about member names must be unique) however TAML does not care about this and it can be turned off with the console variable "$pref::T2D::JSONStrict" (set it to false).
|
12 years ago |
|
MelvMay-GG
|
f784d57b7f
- Minor renaming of the preprocessor definition for the asset-scope token.
|
12 years ago |
 Mich
|
a20f2864a1
- First push of Torque 2D 2.0 (MIT)
|
12 years ago |
