* Greg Hawkes -- Friday 02 May 2008: > Just so that I understand: are you saying that I should have created the > trafficlist file using proved and maintainable methods?
No. (Though proved methods are always good. :-) > Or, are you saying that the Traffic Manager should use the proved and > maintainable XML parser, and should not use its own parser? There really is only one parser, and it works correctly, as far as I can say. But there are different places that interface to that parser. The standard way is the <PropertyList> reader. It works well and is supported by lots of tools. Nasal code can easily read such files using just one command. The file contents can be copied to the/a property tree and be modified or saved from there. And then there are readers for custom XML formats (non-<PropertyList> ones), such as in YASim or the traffic manager, the latter of which has this bug. * Durk Talsma -- Friday 02 May 2008: > Melchior is suggesting I should have used a different method for > parsing the traffic files. :-) I'm stating that, not just suggesting. :-P The refusal to use the standard ways is IMHO bad for FlightGear. This shouldn't have passed code review. Had you used <PropertyList>s, with proper geo coords (not the very unpractical "S37 37.103" format), then we could easily load a parking.xml file into FlightGear, edit the slots there in UFO mode, and save the file again. We are limiting our possibilities by disregarding consistency. It always bites us in the butt later. m. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Flightgear-users mailing list Flightgear-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-users
