Immediate mode GUI
This article may be too technical for most readers to understand. Please help improve it to make it understandable to non-experts, without removing the technical details. (August 2017) (Learn how and when to remove this template message)
An immediate mode graphic user interface (GUI), also known as IMGUI, is a graphical user interface design pattern which uses an immediate mode graphics library to create the GUI. The other major pattern of API design in graphics libraries is the retained mode.
This section does not cite any sources. (August 2020) (Learn how and when to remove this template message)
For game implementation, a GUI should
- be updated in sync with the game scene or complex graphic.
- be overlaid on a game scene or complex graphic (which is especially easy in both cases, when both GUI and game scene are controlled by the game loop).
- have an unusual appearance or be pepped with complex graphic. This implies that in an immediate mode GUI, the client code is holding its own rendering primitives and API design which affects the graphics pipeline implementation.
- is more direct in the sense that the widget tree is often a function call tree that is compostable and flexible but hard to interact with.
- is less complex and easier to understand (in terms of fewer implicit assumptions per toolset API call). This usually also results in less functionality.
- is more elaborate to create and manage (typically needs more tool set API calls) if more than a simple widget tree, including layout (absolute and relative positioning referring to parent or siblings).
- has less sophisticated occlusion culling (z-buffering), hit-testing, state change handling, scrolling, and focus/hot control (widget) animations. This also implies the need to manage the logical tree/visual tree itself.
- has to rebuild the vertex buffers completely from scratch for each new frame.
- can put a constant workload on the CPU if not utilizing shaders loaded on the GPU.
Immediate mode GUI widget toolkits are a good choice for those who prefer a simple, easily changeable, and extendable GUI toolkit. They are usually generic, open-source, and cross-platform. One way to have the flexibility and composability of an immediate mode GUI without the disadvantages of keeping the widget tree only in function calls, with the lack of direct control of how the GUI is drawn in the rendering engine would be to use a virtual widget tree, just like React uses a virtual DOM.
Other types of Immediate Mode GUI
- nuklear with backends for several graphics libraries (Direct3D, GLFW, OpenGL, SDL, SFML, Wayland, Windows DGI, Window GDI+ and X11)
- kiss_sdl for SDL (Simple Direct Media Layer)
- Gio for Go
- Dear ImGui written in C++ with back-ends for several graphics APIs (Allegro 5 , DirectX, GLFW, iOS, Marmalade, Metal, OpenGL, SDL 2 and Vulkan), that also has
- Radich, Quinn (May 30, 2018). "Retained Mode Versus Immediate Mode". Win32 apps. Microsoft. Retrieved 21 December 2019.
- Mononen, Mikko (2019-12-18). "AdrienHerubel/imgui: A small multiplatform immediate mode graphical user interface with OpenGL3.2 backend".
- Mettke, Micha (2019-12-22). "vurtun/nuklear: A single-header ANSI C gui library".
- Korrovits, Tarvo (2019-12-19). "actsl/kiss_sdl: Simple generic GUI widget toolkit for SDL2".
- "Gio - immediate mode GUI in Go". gioui.org. Retrieved 2019-11-14.
- Cornut, Omar (2019-12-22). "ocornut/imgui: Dear ImGui: Bloat-free Immediate Mode Graphical User interface for C++ with minimal dependencies".
- kotlin-graphics (2019-12-19). "kotlin-graphics/imgui: Bloat-free Immediate Mode Graphical User interface for JVM with minimal dependencies (rewrite of dear imgui)".