Navy.gif/imgui
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated About the IMGUI paradigm (markdown)

omar 2021-02-15 12:34:00 +01:00
parent aaa16e825e
commit 12788b9c21
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
About-the-IMGUI-paradigm.md

@ -39,8 +39,8 @@ The existence of those two terms effectively has hindered both discussions and r
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 to retain lots of artifacts from the UI library (e.g. create objects, maintain references). - Often have the app/programmer retain artifacts from the UI library (e.g. create objects, maintain references).
- Often have the UI library retain app/programmer data in widgets, requiring synchronization mechanisms. - Often have the UI library retain app/programmer data in UI widgets, requiring synchronization mechanisms.
What it doesn't stands for: What it doesn't stands for:
@ -54,7 +54,7 @@ What it doesn't stands for:
- IMGUI does not means that layout features are limited. - IMGUI does not means that layout features are limited.
- IMGUI does not means that there is a single pass flow. - IMGUI does not means that there is a single pass flow.
TODO: Each of those points should be explained with a paragraph. We could also describe how common UI libraries (of all types) stand on a given axis. TODO: Each of those points should be explained with a paragraph. We could also describe how common UI libraries (of all types) stand on a given axis. We could also described less explored paths and envision what new UI libraries could do.
### Vurtun's writeup ### Vurtun's writeup