> Sent: 25 October 2007 14:10 > To: flightgear-devel@lists.sourceforge.net > Subject: Re: [Flightgear-devel] FlightGear/Plib periodic stutter notes > > > * Torsten Dreyer -- Thursday 25 October 2007: > > To make things easier for developers, can we think of a > plug-in system > > for callbacks so a potential developer write a library that > is linked > > in dynamically by the flightgear core? > > No. > > That would mean to add and maintain plug-in loader code for > all supported platforms, as well as hundreds of lines of > documentation, for people who are bright enough > > - to set up a development environment > - to understand enough of fgfs internals to write a module > - that follows an interface API specification > > but are too stupid > > - to add three lines to a Makefile.am > - one line to fg_init.cxx and > - one line to main.cxx > > Such a feature wouldn't make developing one bit easier or > faster -- quite on the contrary. And it would lead in no time > to Windows/Linux/Mac-*only*, binary *only* addons. Sure, the > GPL would prohibit to run such modules with fgfs, and Curt > would be happy to sue all infringers (because he has too much > time and too much money. :-) > > This is not where we want to go. (As far as I'm concerned, > but I don't speak for the project.) >
And to add my two pence worth, I have never had the slightest dificulty in getting new or amended code into fg, provided that it was: A. Justified B. Worked. There has been the odd difficulty over style, indents, and tabs. But let's not go there. Vivian ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
