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

Jump to navigation Jump to search

Howto:Processing legacy PUI dialogs using Canvas (view source)

Revision as of 08:06, 8 July 2017

1 byte added ,  8 July 2017
no edit summary
No edit summary
No edit summary
Line 15: Line 15:
{{FGCquote|1= Qt widgets can be drawn into OpenGL buffers. That doesn't change the fact that it would be a great deal of work to port our GUI to Qt, and it would introduce a very large external dependency. Having seen the fit pitched when I started using boost... Now, big projects can get done, and motivated individuals with time on their hands can work wonders. We should keep in mind the relative importance of the GUI system to the whole flying experience and judge whether it would be worth the effort to do a huge rewrite in this area.|2= {{cite web  | url    = http://sourceforge.net/p/flightgear/mailman/message/24467194/  | title  = <nowiki>Re: [Flightgear-devel] GUI dialogs suck</nowiki>  | author = <nowiki>Tim Moore</nowiki>  | date  = Jan 30th, 2010  }}}}
{{FGCquote|1= Qt widgets can be drawn into OpenGL buffers. That doesn't change the fact that it would be a great deal of work to port our GUI to Qt, and it would introduce a very large external dependency. Having seen the fit pitched when I started using boost... Now, big projects can get done, and motivated individuals with time on their hands can work wonders. We should keep in mind the relative importance of the GUI system to the whole flying experience and judge whether it would be worth the effort to do a huge rewrite in this area.|2= {{cite web  | url    = http://sourceforge.net/p/flightgear/mailman/message/24467194/  | title  = <nowiki>Re: [Flightgear-devel] GUI dialogs suck</nowiki>  | author = <nowiki>Tim Moore</nowiki>  | date  = Jan 30th, 2010  }}}}


As of 05/2017, James is still very much undecided about which technology to use for in-sim GUI, he is somewhat inclined towards using the Canvas, because it avoids some rendering issues (but exposes a few more, + some performance ones) but the problem is James is fairly unhappy with the GUI / widget API in the Canvas right now - it does not satisfy my ideas about how simple + robust such an API should be, James needs to evaluate if the current API can be improved or needs to be drastically changed. The other issue is to use QtQuick rendered into OpenGL, which has a very nice robust and well-designed API, but adds some dependencies and complicates the rendering architecture, which makes him nervous about multi-window setups and other more esoteric OSG configs.<ref>{{cite web
As of 05/2017, James is still very much undecided about which technology to use for in-sim GUI, he is somewhat inclined towards using the Canvas, because it avoids some rendering issues (but exposes a few more, + some performance ones) but the problem is James is fairly unhappy with the GUI / widget API in the Canvas right now - it does not satisfy his ideas about how simple + robust such an API should be, James needs to evaluate if the current API can be improved or needs to be drastically changed. The other issue is to use QtQuick rendered into OpenGL, which has a very nice robust and well-designed API, but adds some dependencies and complicates the rendering architecture, which makes him nervous about multi-window setups and other more esoteric OSG configs.<ref>{{cite web
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/35863607/  
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/35863607/  
   |title  =  <nowiki> Re: [Flightgear-devel] KBOS runway list? are there 10 or are there
   |title  =  <nowiki> Re: [Flightgear-devel] KBOS runway list? are there 10 or are there
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/108817"

Navigation menu