Melchior FRANZ wrote: > I've started to clean up the HUD code. I've moved all class-specific > code to the classes. Before, each class had an external initializer > that loaded the properties from the property tree and called a constructor > with *many* parameters. Now the constructors are only pointed to the > group node and fetch their stuff themselves. Now there are two questions: > > 1. I would like to create a HUD class that contains the generic > stuff (like setup, context, switching etc.), all of which is currently > a set of separate static functions. Should this be: > > (a) an FGInstrumentMgr controlled class instance, and if so: should it > be moved to Instrumentation/HUD/?
That's my preference, especially since it will be a completely overhauled version of the HUD code. > 2. I want to drop the unflexible <loadfn> getters, and use <property> > instead, so that any HUD element can take its value from any property. > The current, ugly way is AFAIK due to the fact that the HUD code > predates the property code, so there wasn't much choice for the author > back then. Today really only properties make sense. Bravo! (Applause arises). > (d) can I simply switch to properties, if I make sure that all HUD > files in CVS get converted, and the result is identical (or otherwise > in agreement with the aircraft maintainer)? Or am I expected to > support both methods for one or two releases? I'm trying to guess how many newly created special HUD configurations can be. I think there are at least a few. So I would postpone dropping the old code to after 1.0 (maybe not even counting 1.x subversions). > My preference is, of course, to switch and let <loadfn> die immediately. > :-) Yes, I can imagine but I think the cases where the old code is/has been used outside of the FlightGear scope are all cases that draw attention to FlightGear (universities and research organizations). I would just copy the current code to a new location and rename it's class to maybe XMLHUD or something. Erik -- http://www.ehtw.info (Dutch) Future of Enschede Airport Twente http://www.ehofman.com/fgfs FlightGear Flight Simulator _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
