Hi again !
I am just about trying to add some test-hooks to FlightGear, but wouldn't like to have to rebuild the whole FlightGear build tree each time (~ 350 MB ), just for 2-3 added small test-functions, hence I came up with the following idea:
How about adding a sub-directory "lib" to FlightGear/data/Nasal which could then keep plugins that implement external Nasal functions ?
That way one wouldn't need to rebuild FlightGear itself in order for a certain feature to be added and you could even keep code separated, in addition one would not necessarily need to have the whole buildtree available in order to implement a specific function for Nasal.
And you could still optionally import that plugin code natively into FlightGear-if you want to- it wouldn't make any difference in the end.
One would only need to implement some kind of simple plugin structure and a simple mechanism to load all libraries in a specific subfolder and check whether they export a specific Plugin-function - if they do, these functions will be made available as Nasal Commands.
One could even go further and use the same technique in order to implement external fgcommands for FlightGear.
What do you think ?
----------- Boris
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
