Using "api", using "UI system"
parent
12788b9c21
commit
b0de2ceb42
@ -33,14 +33,14 @@ The existence of those two terms effectively has hindered both discussions and r
|
|||||||
|
|
||||||
@ocornut's attempt for a definition (WIP, 2021)
|
@ocornut's attempt for a definition (WIP, 2021)
|
||||||
|
|
||||||
- IMGUI refers to the **interface** between the app/programmer and the UI library.
|
- IMGUI refers to the api: literally the interface between the application and the UI system.
|
||||||
- The interface tries to minimize the app/programmer having to retain data from the UI library.
|
- The api tries to minimize the application having to retain data from the UI system.
|
||||||
- The interface tries to minimize the UI library having to retain data from the app/programmer.
|
- The api tries to minimize the UI system having to retain data from the application.
|
||||||
|
|
||||||
This is in comparison with typical RMGUI ("retained-mode UI") which:
|
This is in comparison with typical RMGUI ("retained-mode UI") which:
|
||||||
|
|
||||||
- Often have the app/programmer retain artifacts from the UI library (e.g. create objects, maintain references).
|
- Often have the application retain artifacts from the UI system (e.g. create objects, maintain references).
|
||||||
- Often have the UI library retain app/programmer data in UI widgets, requiring synchronization mechanisms.
|
- Often have the UI system retain appplication data in UI widgets, requiring more synchronization mechanisms.
|
||||||
|
|
||||||
What it doesn't stands for:
|
What it doesn't stands for:
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user