Hi Ralf, Ralf Gerlich wrote:
>>Well, there is the problem: if you want to database the highest level >>layout info, you need to standardize the high level model. > Then that's where we need to work with you and Robin Peel regarding the > next generation database ;-) Just to play devil's advocate: 1. How hard would it be to reconstruct a layout from the low-level apt.dat layout? I'm imagining a layout started in WorldEditor and then modified in TaxiDraw. Would you and I have to agree on a high-level interchange format, or could we reconstitute the info we need from the low level format? (I suppose this is a question about the editors - for an editor that truly built layouts from centerlines, there would I think be no way to reconstitute a layout. Because WED will be area-focused, it could probably rebuild a layout from its export, with the risk that some layouts would be invalid within WED.) 2. What if we databased the last author of a layout...the implication being that if you want to edit a layout in the DB and cannot work with the final apt.dat data, you contact the author and resolve the problem directly? Without this, it becomes necessary for all editors to agree on a high level format that is in the DB and thus is involved in lockstep. So I'm looking for a practical solution that would decouple this dependency. *cheers* Ben -- Scenery Home Page: http://scenery.x-plane.com/ Scenery blog: http://xplanescenery.blogspot.com/ Plugin SDK: http://www.xsquawkbox.net/xpsdk/ Scenery mailing list: [EMAIL PROTECTED] Developer mailing list: [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
