On Friday, 22 October 2004 10:28, Boris Koenig wrote:
Despite from that I don't like the idea too much, either - personally I am not that much into Java, and even though its platform-independence is a nice thing, it's really a bit awkward to make Java integrate with existing applications, and then there's the performance issue, too - even without time-critical applications, you'd always need to have a whole VM running - probably not a good option if you want to run something like FG, too.
Why would you want to run an Installer and FlightGear at the same time?
Surely FlightGear would only be launched after the installer has done it's job and exited?
And I don't see performance as an issue - installers don't need to do tons of number crunching. If the install takes an extra 30 seconds so what.
I'm not a real Java fan myself but Java is the closest cross platform environment/tookit that we have at the moment.
All other toolkits like wxWidgets (used to be wxWindows till MS chewed them out), GTK, Python, Tcl/Tk, etc need to be installed first and the installation process often does not go smoothly.
Why does is need to be a seperate installer? There's nothing wrong with packaging up the aircraft in exactly the same way as the binaries? At least that way the files can be managed by whatever tools are available on the system in the first place.
-- Jon Stockill [EMAIL PROTECTED]
_______________________________________________ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
