20,741
edits
FlightGear plugins: Difference between revisions
Jump to navigation
Jump to search
m
→Background
m (→Background) |
|||
| Line 22: | Line 22: | ||
| author = <nowiki>Lydiot</nowiki> | | author = <nowiki>Lydiot</nowiki> | ||
| date = Dec 15th, 2015 | | date = Dec 15th, 2015 | ||
}} | |||
}} | |||
{{FGCquote | |||
|1= its not that easy to get your changes into the system. I am not complaining about this and I acknowledge that changing the internal program is a thing that has to be carefully reviewed. Writing some Nasal code usually does not affect the whole system and can be maintained for a single aircraft. 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? I think having a plug-in system for compiled/binary extensions whould give us great flexibility without touching the flightgear-core to heavily. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/15645373/ | |||
| title = <nowiki>Re: [Flightgear-devel] FlightGear/Plib periodic stutter notes</nowiki> | |||
| author = <nowiki>Torsten Dreyer</nowiki> | |||
| date = Oct 25th, 2007 | |||
}} | }} | ||
}} | }} | ||