Currently RenderToolbox3 uses custom text formats for mappings and conditions files. In some ways these are "natural" and easy for humans to edit.
But we often want to manipulate them programmatically as well. We have custom parsing and printing code that allows us to create or edit conditions files in memory. We have custom parsing code for mappings files, but no good way to write parsed mappings files back to file.
Instead of developing and maintaining these custom parsers and printers, why not use XML? We would define an XML format/schema for conditions files and one for mappings files. Then we could take advantage of existing XML tools for reading, writing, and editing the files. These tools would include Java-based JDOM as well as RenderToolbox3 SceneDOM utilities.
Currently RenderToolbox3 uses custom text formats for mappings and conditions files. In some ways these are "natural" and easy for humans to edit.
But we often want to manipulate them programmatically as well. We have custom parsing and printing code that allows us to create or edit conditions files in memory. We have custom parsing code for mappings files, but no good way to write parsed mappings files back to file.
Instead of developing and maintaining these custom parsers and printers, why not use XML? We would define an XML format/schema for conditions files and one for mappings files. Then we could take advantage of existing XML tools for reading, writing, and editing the files. These tools would include Java-based JDOM as well as RenderToolbox3 SceneDOM utilities.