UI Unification: Difference between revisions

Jump to navigation Jump to search
Line 29: Line 29:


== Motivation ==
== Motivation ==
Note that Qt is supposed to be optional - so what do we do if Qt isn't added at compile time?<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/34536489/
  |title  =  <nowiki> Re: [Flightgear-devel] GUI questions (again) </nowiki>
  |author =  <nowiki> Thorsten Renk </nowiki>
  |date  =  Oct 13th, 2015
  |added  =  Oct 13th, 2015
  |script_version = 0.40
  }}</ref>
If a siable number of core developers has argued against making Qt a dependency and there's a consensus to confine its use to a GUI module, then there are legitimate concerns<ref>{{cite web
  |url    =  https://sourceforge.net/p/flightgear/mailman/message/34537005/
  |title  =  <nowiki> Re: [Flightgear-devel] GUI questions (again) </nowiki>
  |author =  <nowiki> Thorsten Renk </nowiki>
  |date  =  Oct 13th, 2015
  |added  =  Oct 13th, 2015
  |script_version = 0.40
  }}</ref>
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 existin dialog [[PUI]]/XML syntax.  
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 existin dialog [[PUI]]/XML syntax.  


Navigation menu