20,741
edits
Emesary: Difference between revisions
Jump to navigation
Jump to search
m
→JavaScript port
(→Intro) |
|||
| Line 79: | Line 79: | ||
== JavaScript port == | == JavaScript port == | ||
Torsten is successfully using JavaScript via nodejs for a private project with FlightGear. Communication with FGFS runs via websocket and the http/fgcommand interface, everything works as one would expect; the same technique would be possible with Python or any other scripting language that supports websockets, http-get, http-post and has some support for JSON (python has, ruby has, lua has).<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34792963/ | |||
|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> | |||
Almost every system should be able to run completely independently of the frame rate. What of course would be mandatory is to sync properties at well defined time stamps, this is what the RTI takes care of. <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34796183/ | |||
|title = <nowiki> Re: [Flightgear-devel] Designing a thread-safe property tree API | |||
(was Re: A FGPythonSys implementation: ...) </nowiki> | |||
|author = <nowiki> Torsten Dreyer </nowiki> | |||
|date = Jan 26th, 2016 | |||
|added = Jan 26th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
almost every system should be able to run completely independently of the frame rate. What of course would be mandatory is to sync properties at well defined time stamps, this is what the RTI takes care of. <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34796183/ | |||
|title = <nowiki> Re: [Flightgear-devel] Designing a thread-safe property tree API | |||
(was Re: A FGPythonSys implementation: ...) </nowiki> | |||
|author = <nowiki> Torsten Dreyer </nowiki> | |||
|date = Jan 26th, 2016 | |||
|added = Jan 26th, 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 | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34793778/ | |||
|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> | |||
{{WIP}} | {{WIP}} | ||