20,741
edits
Reset & re-init: Difference between revisions
Jump to navigation
Jump to search
→Benefits
No edit summary |
|||
| Line 89: | Line 89: | ||
** Since it's a new property tree, we have to destroy and restart the Nasal context anyway. This should greatly simplify aircraft Nasal script development. | ** Since it's a new property tree, we have to destroy and restart the Nasal context anyway. This should greatly simplify aircraft Nasal script development. | ||
* Separate startup GUI frontends like fgrun may become obsolete or at least optional eventually, because FlightGear itself would become increasingly runtime-configurable ([[FlightGear Sessions#The FlightGear Frontend Debacle|we have about 10-15 GUI launchers for FG currently]]). | * Separate startup GUI frontends like fgrun may become obsolete or at least optional eventually, because FlightGear itself would become increasingly runtime-configurable ([[FlightGear Sessions#The FlightGear Frontend Debacle|we have about 10-15 GUI launchers for FG currently]]). | ||
** once FlightGear can be propertly re-initialized, providing a [[Canvas]]-based GUI on top would be fairly simple | ** once FlightGear can be propertly re-initialized, providing a [[Canvas]]-based GUI on top would be fairly simple, see [[Aircraft Center]] | ||
** this should help improve end user usability - because FlightGear would become more self-contained, without inevitably requiring external tools to provide basic GUI configurability. | ** this should help improve end user usability - because FlightGear would become more self-contained, without inevitably requiring external tools to provide basic GUI configurability. | ||
** given the number of separate FlightGear launchers, there are also lots of developers involved in developing and maintaining these external software packages, some of them also active FlightGear core developers/contributors - so this step could further help channel important development resources, to focus on the main project, i.e. fgfs. | ** given the number of separate FlightGear launchers, there are also lots of developers involved in developing and maintaining these external software packages, some of them also active FlightGear core developers/contributors - so this step could further help channel important development resources, to focus on the main project, i.e. fgfs. | ||