20,741
edits
(→Status) |
|||
Line 443: | Line 443: | ||
}} | }} | ||
}} | }} | ||
<references/> | <references/> | ||
=== Python in FlightGear === | |||
{{See also|Python in FlightGear}} | |||
{{See also|FGPythonSys}} | |||
{{FGCquote | |||
|1= depending on how much progress bugman is going to make with his "python-integration-in-FlightGear" experiments (FGPythonSys), we may at some point even be able to ship FFGo as part of FGData (e.g. $FG_ROOT/Python/Apps/FFGo) and run it via FGPythonSys directly | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=275910#p275910 | |||
| title = <nowiki>Re: Announcing </nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Feb 12th, 2016 | |||
| added = Feb 12th, 2016 | |||
| script_version = 0.25 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= if this FGPythonSys were integrated into FG, doing things in Python that are directly committed to the core (properly reviewed---well, as the C++ code) as opposed to coming from various uncontrolled external places would certainly be pretty interesting | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=275923#p275923 | |||
| title = <nowiki>Re: Announcing </nowiki> | |||
| author = <nowiki>rominet</nowiki> | |||
| date = Feb 13th, 2016 | |||
| added = Feb 13th, 2016 | |||
| script_version = 0.25 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= The built-in launcher that James is writing would seem to me to be a good candidate for doing things in Python (assuming there are good bindings to the C++ data structures): you need high-level access to FG aircraft and airport data, it is not performance critical, the need for threading is certainly rather limited, the code does not come from a random hangar and can be audited just like the C++ code when committed, probably by more people actually. Add to this that PyQt works very well (I have had a very pleasant experience with PyQt 3&4 under Python 2&3, and if I get enough time, I'll maybe port FFGo to PyQt---Tk is useful, clearly, but frustrating; for example Qt's QAbstractItemModel and QAbstractItemView were great to manage non-trivial tablular data; with Tk, table/tree cells are just strings and your program has to manage on its own to link that to the nice high-level Python data structures). | |||
(and I have tried other toolkits before Qt and Tk, namely GTK+ 1.2 and wxWidgets [around 2003] Bottom line: for me, Qt is the best) | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=275923#p275923 | |||
| title = <nowiki>Re: Announcing </nowiki> | |||
| author = <nowiki>rominet</nowiki> | |||
| date = Feb 13th, 2016 | |||
| added = Feb 13th, 2016 | |||
| script_version = 0.25 | |||
}} | |||
}} | |||
== Testing == | == Testing == |