20,741
edits
FGPythonSys: Difference between revisions
Jump to navigation
Jump to search
→What is it
(→Status) |
|||
| Line 18: | Line 18: | ||
--> | --> | ||
}} | }} | ||
The point of FGPythonSys is simply implementing something for fun - pretty much the same reason that most things in open source are done. I find that justifying its existence is a little pointless. Anyway, one interesting thing that could be designed would be a set of aircraft base classes in FGData implementing some basic functionality/instruments/systems, etc. Then the aircraft can use OO (object oriented) inheritance to expand on the base class in an aircraft specific way. Of course this could be done in Nasal, but Python's OO design is far more advanced, especially with GC (garbage collection). Not that such arguments are relevant ;) | |||
By the way, I'm thinking that aircraft/content Python would be a restricted subset of the full Python framework. Anyway, all of this is in the realm of fantasy unless people are willing to get their hands dirty and play with C++ code.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=296255#p296255 | |||
|title = <nowiki> Re: Nasal must go </nowiki> | |||
|author = <nowiki> bugman </nowiki> | |||
|date = Oct 8th, 2016 | |||
|added = Oct 8th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
== What is it == | == What is it == | ||