On 6/29/06, Kai Sterker <[EMAIL PROTECTED]> wrote:
I'm wondering ... any editor should be able to write data files that are directly usable by the engine. Basically, there are/will be two formats that are equivalent. A binary format and a ASCII format (which needs a few tweaks and a functional parser yet).
That's good to know.
Internally, all data is stored as key/value pairs, meaning that the order in which stuff appears does not matter so much (although reading the data will be fastest if things are saved in the order they will be loaded). The structure of the data does matter though, since elements can be nested. Since we do not know exactly how the data for characters are loaded by the engine, it is a little difficult to have any (prototype) editor generate the data. OTOH, it should be quite easy to change or convert data once we know the format.
At this point, the 'output' consists of some labels in a pane at the bottom of the screen. Their captions change as the data changes. I'm not ready to worry about file formats or even file handling. But yes, once we decide on a file format, we can teach the editors to read it. I merely proposed XML because it lends itself to structured data, (including key/value pairs, I think) can be checked for data integrity via DTD, and logically compliments my original Perl/CGI/HTML idea. I'm actually prototyping in C++, though. _______________________________________________ Adonthell-devel mailing list Adonthell-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/adonthell-devel