Aircraft dialogs: Difference between revisions

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).
Another reason being, all sim-specific dialogs can be taken care of by the respective GUI creators/frontends (Qt, Phi, PUI), and for instance it doesn't really matter how the detailed implementation of, say the weather selection, is in Phi vs. Qt as long as they do the same thing. But aircraft-specific dialogs are not under the control of the GUI creators. <ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/34532750/
  |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>
Using the Canvas also for the GUI provides the advantage of a unified rendering backend for any type of GUI/text rendering and also the ability to use the same widgets everywhere - eg. use them also inside aircraft for CDU GUIs or other displays...<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/29584553/
  |title  =  <nowiki> Re: [Flightgear-devel] Switching from PUI to osgWidget </nowiki>
  |author =  <nowiki> Thomas Geymayer </nowiki>
  |date  =  Jul 24th, 2012
  |added  =  Jul 24th, 2012
  |script_version = 0.36
  }}</ref>


Which means, Canvas for aircraft specific in-window options and Phi for instructor stations. Canvas has the advantage for aircraft developers to make really aircraft specific options available. These vary so much across the board that Qt won't be able to address them anyhow, [...] like the 3d option that Canvas provides. <ref>{{cite web
Which means, Canvas for aircraft specific in-window options and Phi for instructor stations. Canvas has the advantage for aircraft developers to make really aircraft specific options available. These vary so much across the board that Qt won't be able to address them anyhow, [...] like the 3d option that Canvas provides. <ref>{{cite web