Tony Peden writes: > IMO, the logging options should be moved off to a separate file and > no version of that file should be committed to base CVS. > That way, no user will ever get logging when they don't want it and > developers can set things up the way they like for *all* JSBSim > aircraft.
Moving the logging request to a separate file seems reasonable to me. Maybe you could even have several logging.xml files to specify different subsets of data which you might be interested in looking at depending on what you were working on at the time ... log-gear.xml, log-engine.xml, etc. I don't see any problem commiting these to the base cvs, as long as they aren't activated by default. Having them could be useful if an end user is trying to understand more about what is going on, or wants to send back an accurate/informative bug report or question. This probably involves Jon doing the actual coding work, right? (that is if he agrees with us.) Curt. -- Curtis Olson Intelligent Vehicles Lab FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
