Howto:Processing legacy PUI dialogs using Canvas: Difference between revisions

Jump to navigation Jump to search
m (→‎Widget Support: outdated)
Line 1,153: Line 1,153:


{{FGCquote|1= I don't want to spend too much work in getting PUI and Canvas dialogs working at the same time. The layout and widget systems is now maturing, so I think after 3.2 I can start with porting PUI. Just one major component is missing, namely keyboard input and the according input focus. I guess this will take one or two more releases.|2= {{cite web  | url    = http://sourceforge.net/p/flightgear/mailman/message/32457866/  | title  = <nowiki>Re: [Flightgear-devel] Notes on Aircraft Center...</nowiki>  | author = <nowiki>Thomas Geymayer</nowiki>  | date  = Jun 13th, 2014  }}}}
{{FGCquote|1= I don't want to spend too much work in getting PUI and Canvas dialogs working at the same time. The layout and widget systems is now maturing, so I think after 3.2 I can start with porting PUI. Just one major component is missing, namely keyboard input and the according input focus. I guess this will take one or two more releases.|2= {{cite web  | url    = http://sourceforge.net/p/flightgear/mailman/message/32457866/  | title  = <nowiki>Re: [Flightgear-devel] Notes on Aircraft Center...</nowiki>  | author = <nowiki>Thomas Geymayer</nowiki>  | date  = Jun 13th, 2014  }}}}
{{FGCquote|1= my feeling is that our lowest-effort, most-visually pleasing and consistent result is going to be making both Phi and Qt UIs able to work / translate / parse the dialog XML syntax. |2= {{cite web  | url    = http://sourceforge.net/p/flightgear/mailman/message/34537052/  | title  = <nowiki>Re: [Flightgear-devel] GUI questions (again)</nowiki>  | author = <nowiki>James Turner</nowiki>  | date  = Oct 13th, 2015  }}}}


== Implementation ==
== Implementation ==

Navigation menu