20,741
edits
Aircraft dialogs: Difference between revisions
Jump to navigation
Jump to search
→Background
| Line 5: | Line 5: | ||
After some (partially controversial) discussion, there seems now to be some support for the idea that canvas is a good tool to generate aircraft-specific dialogs in the future <ref>https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/93862C87-0D3E-47BB-B169-8D3CBBF963B7%40kdab.com/#msg36194973</ref> (as it allows to tailor the dialog closely to the plane and also, canvas being canvas, the UI can smoothly mesh with the 3d models, so you can project a canvas checklist onto a 3d model in sim for instance rather than a popup window). | After some (partially controversial) discussion, there seems now to be some support for the idea that canvas is a good tool to generate aircraft-specific dialogs in the future <ref>https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/93862C87-0D3E-47BB-B169-8D3CBBF963B7%40kdab.com/#msg36194973</ref> (as it allows to tailor the dialog closely to the plane and also, canvas being canvas, the UI can smoothly mesh with the 3d models, so you can project a canvas checklist onto a 3d model in sim for instance rather than a popup window). | ||
Also, even if we manage to come up with a way to define dialogs such that they can be parsed and executed in both Phi and Qt, someone would have to do this for possibly unmaintained aircraft as well and bring them up to speed.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/34534099/ | |||
|title = <nowiki> Re: [Flightgear-devel] GUI questions (again) </nowiki> | |||
|author = <nowiki> Thorsten Renk </nowiki> | |||
|date = Oct 12th, 2015 | |||
|added = Oct 12th, 2015 | |||
|script_version = 0.36 | |||
}}</ref> | |||
Besides, there's often (though not always) a close relationship between in-cockpit displays and aircraft-specific dialogs, i.e. having a canvas-based system the default for aircraft dialogs, such as to render MFDs inside dialog windows and these things. Has the advantage that it has been demonstrated to cope with the [[Pui2canvas|PUI/XML]] - so relatively little action for currently unmaintained planes needed. Has the disadvantage of being a tad confusing visually perhaps.<ref>{{cite web | Besides, there's often (though not always) a close relationship between in-cockpit displays and aircraft-specific dialogs, i.e. having a canvas-based system the default for aircraft dialogs, such as to render MFDs inside dialog windows and these things. Has the advantage that it has been demonstrated to cope with the [[Pui2canvas|PUI/XML]] - so relatively little action for currently unmaintained planes needed. Has the disadvantage of being a tad confusing visually perhaps.<ref>{{cite web | ||