> That's exactly what I started doing but ... > > Problem 1 (external app) : > Having the training session as a separate network app instead of being > integrated into FG is going to put off a lot of less technically minded > people. > It requires that the user first install Python + pyao + pyogg + pyvorvis. > Then they have to install the training packages and try to start FG together > with the simulator. > I'd much rather code it in Nasal have it part of the FG package itself or as > an addon that can be unzipped into the FG tree and run as is.
If it is easier for you to develop & maintain externally, I think you can stop bothering about the less technically minded people. Anything with package dependency tracking capability (like any modern linux distribution) will automatically pull the relevant software in. The more technically minded folks will be able to install the relevant packages for manual compilation, and the rest will wait for a prepared distribution package with the proper dependencies in. (I am unsure though if this might strain the win32 bundling process significantly, though. Surely Frederic knows?) Vassilii ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
