Curtis Olson wrote: > 2009/3/20 Mathias Fröhlich wrote: > > Ok. > But from my point of view the property tree is also used as a reflection > framework to reflect objects state into the > models/scripting/whatever. From my > point of view, the serialization of the objects into xml is just a > special > case of that reflection stuff. Given that, you might consequently > want to reflect > more complex types by the properties. > > > The aggregate types are all constructed as combinations of our simpler > types. I think what I would propose is we could add an API layer which > could read or write a node as an aggregate type, but internally it would > map these complex types to a parent node with several children. So our I'll repeat that the code to translate back and forth between our current property node aggregates and aggregate C++ types is not a real problem coding-wise. I just don't like the current XML syntax.
Tim ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
