Thomas Förster wrote:

I also thought about this as an option for a GUI. The main advantage would be that this approach ensures there's no GUI code in FG and there is a well designed API/Protocol to it. Writing alternative GUI's should be easy using that API/Protocol. Having the GUI seperated also makes it easy to distribute the apps across machines, i.e. having a simulator with an instructors workplace (changing weather, fail engines...)

With the added advantage of not bloating the simulator - gets my vote.

Jon Stockill

Flightgear-devel mailing list

Reply via email to