On Wednesday 08 April 2009, Durk Talsma wrote: > On Tuesday 07 April 2009 21:28:34 syd adams wrote: > > This is getting over my head ... but I'd prefer not to see FG > > stagnate because of fear of the unknown ... it sounds like an > > interesting idea .... but I dont understand the code as well as > > some others and dont see the apocolypse coming :) > > Syd pretty well summarized my own stance on this. Let me just add > a few thoughts: > > Just the fact that a few extensions of the existing property > types can have a positive impact on rendering speed, as I judge > from Tim's original proposal should be enough to at least allow > us to experiment with this. I presume that if we really run into > trouble somewhere down the line, we can always fix the offending > parts in the process, or switch over to something more along the > lines of the current architecture.
I've been following this but I don't remember anyone, in either camp, pointing out where it brings a significant performance increase, or where the failure to adopt it will result in a significant performance drop. I specifically asked about this in one of my earlier posts but if anyone answered I must have missed their replies. As for the idea that the new datatypes should be adopted on the principle that if they do turn out to cause problems they can be fixed later, well, no offence intended Durk, but that just seems extremely foolhardy to me. Planned development? - we've heard of it. > Secondly, the fact that we do have additional property types > certainly doesn't mean we have to use them in situations were the > existing solution would suffice. It seems to me that Tim has > adequately addressed any potentials concerns raised in this area. > > Cheers, > Durk Is there going to be anything to stop people from using them where the existing solution would suffice or will we be able to use either format in any situation when we want to specify linked data? For example, if we can specify RGB values using a vec3 datatype, will we be able to use that datatype for XYZ values? If we can't, what will happen when, and not if, someone someone tries to do so? If the new datatypes cannot be used everywhere, is there going to be somewhere in the documentation that lists exactly where it can and can't be used, baring in mind that it is normal to add new branches and nodes to the tree as required? LeeE ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
