20,741
edits
FGPythonSys: Difference between revisions
Jump to navigation
Jump to search
→Status
(→Status) |
|||
| Line 354: | Line 354: | ||
== Status == | == Status == | ||
the focus of the efforts in my experimental [https://forum.flightgear.org/viewtopic.php?f=6&t=28378&p=289080&hilit=python#p289080 FGPythonSys branches] is more to provide a Python interface to core FlightGear programming rather than replace Nasal. For example one aim is to convert the whole of the SimGear programming interface (API) into a Python library. Another is to expose the subsystem interface to allow for Python modules to create new FlightGear subsystems. As a biarre aside, if FGPythonSys was designed to replace Nasal, it would also be able to fully replace the XML parts of aircraft as well. | |||
In any case, I have been a bit busy with RL and there is no one helping in the task of advancing FGPythonSys. So at this rate, replacing Nasal with Python will only be a pipe dream for a few content developers.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=296170#p296170 | |||
|title = <nowiki> Re: Nasal must go </nowiki> | |||
|author = <nowiki> bugman </nowiki> | |||
|date = Oct 6th, 2016 | |||
|added = Oct 6th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
{{FGCquote | {{FGCquote | ||
|1= I'm also battling with VS 2015 (msvc14) on a VirtualBox VM with Windows 7. I need to have this system up and running, because Windows support for FGPythonSys is essential. | |1= I'm also battling with VS 2015 (msvc14) on a VirtualBox VM with Windows 7. I need to have this system up and running, because Windows support for FGPythonSys is essential. | ||