PUI: Difference between revisions
(stub) |
mNo edit summary |
||
Line 1: | Line 1: | ||
'''PUI''' is the standard GUI engine used in FlightGear, it is part of Plib and is using raw, fixed-pipeline, OpenGL code internally (no OpenSceneGraph). PUI provides a fairly basic, but robust, set of widgets. | [[File:Custom-autopilot-dialog.png|right|200px]] | ||
'''PUI''' is the standard GUI engine used in FlightGear, it is part of Plib and is using raw, fixed-pipeline, OpenGL code internally (no OpenSceneGraph). PUI provides a fairly basic, but robust, set of widgets. PUI is also used for rendering the [[Menubar]]: | |||
[[File:menubar2.jpg|517px]] | |||
However, PUI related OpenGL code is particularly infamous for causing rendering artifacts for people on AMD/ATI and Intel hardware (especially in combination with certain styles and effects/shaders). | However, PUI related OpenGL code is particularly infamous for causing rendering artifacts for people on AMD/ATI and Intel hardware (especially in combination with certain styles and effects/shaders). | ||
Line 12: | Line 15: | ||
* [[Integrated Web GUI]] (external, browser-based - fully asynchronous) | * [[Integrated Web GUI]] (external, browser-based - fully asynchronous) | ||
* [[Howto:Processing legacy PUI dialogs using Canvas]] (internal, using the [[Canvas]] system and a simple [[Nasal]] parser to deal with existing PUI/XML dialogs) | * [[Howto:Processing legacy PUI dialogs using Canvas]] (internal, using the [[Canvas]] system and a simple [[Nasal]] parser to deal with existing PUI/XML dialogs) | ||
<gallery> | |||
<gallery> |
Revision as of 11:11, 3 November 2015
PUI is the standard GUI engine used in FlightGear, it is part of Plib and is using raw, fixed-pipeline, OpenGL code internally (no OpenSceneGraph). PUI provides a fairly basic, but robust, set of widgets. PUI is also used for rendering the Menubar:
However, PUI related OpenGL code is particularly infamous for causing rendering artifacts for people on AMD/ATI and Intel hardware (especially in combination with certain styles and effects/shaders).
PUI is also known to affect rendering performance quite significantly, while also preventing FlightGear from using a more recent version of OpenGL.
In addition, OpenSceneGraph (OSG) can obviously not help optimize any PUI related GL code.
As of late 2015, there is heavy activity towards creating alternatives to PUI:
- Integrated Qt5 Launcher (depending on Qt5, using multi-threading)
- Integrated Web GUI (external, browser-based - fully asynchronous)
- Howto:Processing legacy PUI dialogs using Canvas (internal, using the Canvas system and a simple Nasal parser to deal with existing PUI/XML dialogs)
<gallery> <gallery>