From 9534bbca7269ee05d61670fab127f6f0ab9865fd Mon Sep 17 00:00:00 2001 From: omar Date: Mon, 15 Feb 2021 14:12:01 +0100 Subject: [PATCH] Working on definition --- About-the-IMGUI-paradigm.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/About-the-IMGUI-paradigm.md b/About-the-IMGUI-paradigm.md index 10ba74e..c4ea7de 100644 --- a/About-the-IMGUI-paradigm.md +++ b/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: