20,741
edits
Modernizing FlightGear Scripting: Difference between revisions
Jump to navigation
Jump to search
Modernizing FlightGear Scripting (view source)
Revision as of 13:22, 8 October 2016
, 8 October 2016→Concerns
| Line 165: | Line 165: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
Do we in the end want a scripting language that is more widely used just > because it is more widely used (which is a disadvantage if you think of > malicious code), because we hope to re-use other code, because there's > less transition time learning a slightly differently syntax?<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34791382/ | |||
|title = <nowiki> Re: [Flightgear-devel] A FGPythonSys implementation: The embedded | |||
Python interpreter as a FlightGear subsystem. </nowiki> | |||
|author = <nowiki> geneb </nowiki> | |||
|date = Jan 24th, 2016 | |||
|added = Jan 24th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
If FlightGear is a sandbox on the playground, how do we dictate which toys are allowed in? If we debate this on purely technical merits, then the argument will literally go on forever in the same sense of Mac vs. PC or iphone vs. android. If we look at it from the standpoint of what toys do people wish to bring into the sandbox to play with, then some of these technical arguments and demanding answers to one's personal level of satisfaction seem a little silly. Prove your truck can haul more sand than the one we already have? Prove your shovel and bucket are better than mine? Do you like yours only because it's red plastic and not yellow?<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34793777/ | |||
|title = <nowiki> Re: [Flightgear-devel] A FGPythonSys implementation: The embedded | |||
Python interpreter as a FlightGear subsystem. </nowiki> | |||
|author = <nowiki> Curtis Olson </nowiki> | |||
|date = Jan 25th, 2016 | |||
|added = Jan 25th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
bringing in the Python toy is potentially harmful for the reaons already stated.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34793861/ | |||
|title = <nowiki> Re: [Flightgear-devel] A FGPythonSys implementation: The embedded | |||
Python interpreter as a FlightGear subsystem. </nowiki> | |||
|author = <nowiki> Torsten Dreyer </nowiki> | |||
|date = Jan 25th, 2016 | |||
|added = Jan 25th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
Instead of adding just-another-feature we need to strip it down to getting a fast and constand fps rendering engine. Everything else needs to run outside the main loop and has to interact with the core by, say HLA/RTI or whatever IPC we have.<ref>{{cite web | Instead of adding just-another-feature we need to strip it down to getting a fast and constand fps rendering engine. Everything else needs to run outside the main loop and has to interact with the core by, say HLA/RTI or whatever IPC we have.<ref>{{cite web | ||
| Line 175: | Line 208: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
== Challenges == | == Challenges == | ||