From bc05fd88216f4e259dcf4695f0d2ea9b1da9c047 Mon Sep 17 00:00:00 2001 From: omar Date: Mon, 15 Feb 2021 13:33:31 +0100 Subject: [PATCH] Updated About the IMGUI paradigm (markdown) --- About-the-IMGUI-paradigm.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/About-the-IMGUI-paradigm.md b/About-the-IMGUI-paradigm.md index da50d77..0b83b1e 100644 --- a/About-the-IMGUI-paradigm.md +++ b/About-the-IMGUI-paradigm.md @@ -34,9 +34,10 @@ The existence of those two terms effectively has hindered both discussions and r @ocornut's attempt for a definition (WIP, 2021) -- 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. +- 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 within the UI system stays within the UI system and isn't part of the definition. This is in comparison with typical RMGUI ("retained-mode UI") which: