On Sat, Mar 21, 2009 at 1:49 AM, Curtis Olson <curtol...@gmail.com> wrote: > > On the flip side, (just my impression), arguing for this change because the > alternative is a more verbose xml syntax is maybe the weakest argument. xml > is already pretty verbose and a percentage difference in verbosity isn't > much of a big deal I don't think.
I share this opinion. In fact, I like that the color components are written out, less possibility for confusion (RGBA? ARGB? BGRA?) At my workplace we use lot of xml files and we avoid parsing text content wherever possible. We mostly use generated xmls, though, so I can accept that if somebody is creating xmls by hand it might be more convenient to just dump all 4 values into a single tag. Having a specialized "color" type instead of vec3d/vec4d seems a better idea to me (if all we are talking about is color). Note also, we *do* write <x-m>0</x-m><y-m>0</y-m><z-m>0</z-m> for position vectors too and nobody died yet :) On the C++ side, I don't object that strongly to adding vector or color types, but adding support for arbitrary types would be more difficult. To bring up MP as an example, we now handle the serialization in the MP code, and not in the property code. For arbitrary types, this would have to change. For the suggested vector types we could still extend the MP code in place, although maintaining backward compatibility might be tricky. I also wonder if property change listeners should get an additional argument, giving the index of the changed item. But of course the change would need to be detected first, which basically means we can not directly expose a writable vec3d/4d contained in the property. (I apologize for not having looked at the code in git yet, feel free to ignore any part of the above that is already addressed by the code) > What other xml tools would read/write our files anyway? "TeXnicer" on the IRC channel has been working on xsl stylesheets for (at least) joystick configuration files, see here for an sample: http://141.76.121.6/~lego/projects/flightgear/X52/demo/Joysticks/Saitek/Jester.xml. I imagine parsing text content from xsl could easily prove a nightmare. Not that I know a sensible application for that right now. -- Csaba/Jester ------------------------------------------------------------------------------ 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
