Cool_Tools/imgui
1
0
Fork 0
mirror of https://github.com/ocornut/imgui.git synced 2024-11-24 07:40:22 +01:00
Code Releases Wiki Activity

Working on definition

omar 2021-02-15 14:12:01 +01:00
parent 68423fff9b
commit 9534bbca72
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
About-the-IMGUI-paradigm.md

@ -36,15 +36,17 @@ The existence of those two terms effectively has hindered both discussions and r
@ocornut's attempt for a definition (WIP, 2021)
What we care about:
- IMGUI refers to the API: literally the interface between the application and the UI system.
- The API tries to minimize the application having to retain data related to the UI system.
- The API tries to minimize the UI system having to retain data related to the application.
- API != Implementation. Whatever happens inside the UI system stays inside the UI system and isn't part of the definition.
- The API tries to minimize the application having to retain data related to the UI system.
- The API tries to minimize the UI system having to retain data related to the application.
- IMGUI does NOT refer to the implementation. Whatever happens inside the UI system stays inside the UI system.
This is in comparison with typical RMGUI ("retained-mode UI") which:
This is in comparison with typical RMGUI ("retained-mode UI"):
- Often have the application retain more artifacts from the UI system (e.g. create objects, maintain references).
- Often have the UI system retain application data in UI widgets, requiring more synchronization mechanisms.
- RMGUI APIs often have the application retain more artifacts from the UI system (e.g. create objects, maintain references).
- RMGUI APIs often require more synchronization mechanisms because the UI system retain more application data.
What it doesn't stands for: