20,741
edits
FlightGear plugins: Difference between revisions
Jump to navigation
Jump to search
→Background
No edit summary |
|||
| Line 48: | Line 48: | ||
| author = <nowiki>Torsten Dreyer</nowiki> | | author = <nowiki>Torsten Dreyer</nowiki> | ||
| date = Oct 25th, 2007 | | date = Oct 25th, 2007 | ||
}} | |||
}} | |||
{{FGCquote | |||
|1= Rather than FlightGear embedding another language, FlightGear would probably benefit much better with a type of loadable module support. Nasal could become one of those modules along with Python and maybe Perl. Much in the same manner that Apache and Apache Modules work. I think that would greatly broaden the horion. | |||
Scripting would be just one type of module, the GUI could be another type which might make it easier to support QT or even Java, not to mention that the FDM code could become a separate module, one for each supported FDM. So in just discussing Python support we may be limiting ourselves and/or FlightGear . | |||
Should we be discussing Module support instead? | |||
Would that greatly reduce the core FlightGear code? | |||
Has module support been discussed before? | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=270770#p270770 | |||
| title = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki> | |||
| author = <nowiki>japreja</nowiki> | |||
| date = Dec 30th, 2015 | |||
| added = Dec 30th, 2015 | |||
| script_version = 0.23 | |||
}} | }} | ||
}} | }} | ||