I'd like to bring up again the issue of standalone FlightGear modules (add-ons, 
plug-ins). You probably hear this question once a while, but I have a new 
argument. ;-)

Although the FlightGear design fairly modular it's provided as a single binary. 
Everyone who wants to create a new I/O module must patch the FlightGear sources 
and compile the FlightGear binary from scratch. This may discourage those who 
want to use FlightGear as a tool and extend it in some way. Moreover, it's not 
always possible to include all functions in a single binary. Some functions may 
be mutually exclusive.

I'm building a FlightGear interface for M&S HLA simulations 
(http://virtualair.sourceforge.net/flightgear.html). There is a single 
standartized C++ API, but many HLA infrastructure (RTI) implementations. To use 
a particular HLA RTI it's necessary to re-compile and re-link FlightGear 
against a particular set of libraries. Thus there can never be a single "HLA 
compliant" FlightGear binary.

To follow the "do things right" rule I think it would be great to implement a 
generic interface for standalone I/O modules. Both Micro$oft FSX and X-Plane 
have such interface. The M&S HLA users would just need to build a shared module 
(.dll or .so) for a particular HLA RTI and load it via the standard FlightGear 
plug-in interface.

If I discuss the design issues with you, implement and test such interface, 
would you accept such interface for the mainline FlightGear?


Flightgear-devel mailing list

Reply via email to