Split Popups, Popovers page into submenu with three pages

Replace the single popups.md with a submenu containing dedicated pages
for Popups, Popover and Built-In popups so each topic gets its own
entry in the sidebar.

Author: claude

docs/.vitepress/config.mjs

@@ -162,7 +162,16 @@ export default defineConfig({
             ],
           },
           { text: "Translation, i18n", link: "/development/translation" },
-          { text: "Popups, Popovers", link: "/development/popups" },
+          {
+            text: "Popups, Popovers",
+            link: "/development/popups/popups",
+            collapsed: true,
+            items: [
+              { text: "Popups", link: "/development/popups/popups" },
+              { text: "Popover", link: "/development/popups/popover" },
+              { text: "Built-In", link: "/development/popups/built_in" },
+            ],
+          },
           {
             text: "Browser Features",
             collapsed: true,

docs/development/popups/built_in.md

@@ -0,0 +1,25 @@
+---
+outline: [2, 4]
+---
+# Built-In Popups
+
+A few pre-built popup classes cover the most common cases:
+
+- `Z2UI5_CL_POP_ERROR`
+- `Z2UI5_CL_POP_FILE_DL`
+- `Z2UI5_CL_POP_FILE_UL`
+- `Z2UI5_CL_POP_GET_RANGE`
+- `Z2UI5_CL_POP_GET_RANGE_M`
+- `Z2UI5_CL_POP_HTML`
+- `Z2UI5_CL_POP_INPUT_VAL`
+- `Z2UI5_CL_POP_ITAB_JSON_DL`
+- `Z2UI5_CL_POP_JS_LOADER`
+- `Z2UI5_CL_POP_MESSAGES`
+- `Z2UI5_CL_POP_PDF`
+- `Z2UI5_CL_POP_TABLE`
+- `Z2UI5_CL_POP_TEXTEDIT`
+- `Z2UI5_CL_POP_TO_CONFIRM`
+- `Z2UI5_CL_POP_TO_INFORM`
+- `Z2UI5_CL_POP_TO_SELECT`
+
+Help expand this collection to cover more cases — contributions are welcome.

docs/development/popups/popover.md

@@ -0,0 +1,41 @@
+---
+outline: [2, 4]
+---
+# Popover
+
+To show a popover, call `client->popover_display` and pass the ID of the control the popover should attach to:
+```abap
+  METHOD z2ui5_if_app~main.
+
+    IF client->check_on_init( ).
+      DATA(view) = z2ui5_cl_xml_view=>factory(
+        )->shell(
+            )->page( `Popover Example`
+                )->button(
+                    text  = `display popover`
+                    press = client->_event( `POPOVER_OPEN` )
+                    id    = `TEST` ).
+      client->view_display( view->stringify( ) ).
+
+    ENDIF.
+
+    CASE client->get( )-event.
+
+      WHEN `POPOVER_OPEN`.
+        DATA(popover) = z2ui5_cl_xml_view=>factory_popup(
+            )->popover( placement = `Left`
+                )->text( `this is a popover`
+                )->button(
+                    id    = `my_id`
+                    text  = `close`
+                    press = client->_event( `POPOVER_CLOSE` ) ).
+        client->popover_display(
+            xml   = popover->stringify( )
+            by_id = `TEST` ).
+
+      WHEN `POPOVER_CLOSE`.
+        client->popover_destroy( ).
+    ENDCASE.
+
+  ENDMETHOD.
+```

docs/development/popups.md docs/development/popups/popups.mddocs/development/popups.md renamed to docs/development/popups/popups.md

@@ -1,13 +1,11 @@
 ---
 outline: [2, 4]
 ---
-# Popups, Popovers
+# Popups
 
-UI5 offers popups and popovers that overlay specific parts of the view. This section walks through building them in abap2UI5.
+UI5 offers popups that overlay specific parts of the view. This section walks through building them in abap2UI5.
 
-### Popup
-
-#### General
+## General
 
 To show a popup, call `client->popup_display` instead of `client->view_display`:
 ```abap
@@ -21,7 +19,7 @@ To show a popup, call `client->popup_display` instead of `client->view_display`:
   ENDMETHOD.
 ```
 
-#### Flow Logic
+## Flow Logic
 A typical popup flow shows a normal view, opens a popup, and finally closes it. Structure it like this:
 ```abap
   METHOD z2ui5_if_app~main.
@@ -55,7 +53,7 @@ A typical popup flow shows a normal view, opens a popup, and finally closes it.
   ENDMETHOD.
 ```
 
-#### Separated App
+## Separated App
 For a cleaner source layout, encapsulate popups in separate classes and call them via [navigation](/development/navigation/navigation).
 
 An example with the confirmation popup:
@@ -83,63 +81,3 @@ An example with the confirmation popup:
 ```
 
 To handle multiple stacked popups, note that abap2UI5 shows only one popup at a time on the frontend. But you can keep a popup stack in your backend logic and re-display the previous popup as needed. See `Z2UI5_CL_DEMO_APP_161`.
-
-### Popover
-To show a popover, call `client->popover_display` and pass the ID of the control the popover should attach to:
-```abap
-  METHOD z2ui5_if_app~main.
-
-    IF client->check_on_init( ).
-      DATA(view) = z2ui5_cl_xml_view=>factory(
-        )->shell(
-            )->page( `Popover Example`
-                )->button(
-                    text  = `display popover`
-                    press = client->_event( `POPOVER_OPEN` )
-                    id    = `TEST` ).
-      client->view_display( view->stringify( ) ).
-
-    ENDIF.
-
-    CASE client->get( )-event.
-
-      WHEN `POPOVER_OPEN`.
-        DATA(popover) = z2ui5_cl_xml_view=>factory_popup(
-            )->popover( placement = `Left`
-                )->text( `this is a popover`
-                )->button(
-                    id    = `my_id`
-                    text  = `close`
-                    press = client->_event( `POPOVER_CLOSE` ) ).
-        client->popover_display(
-            xml   = popover->stringify( )
-            by_id = `TEST` ).
-
-      WHEN `POPOVER_CLOSE`.
-        client->popover_destroy( ).
-    ENDCASE.
-
-  ENDMETHOD.
-```
-
-### Built-in Popups
-A few pre-built popup classes cover the most common cases:
-
-- `Z2UI5_CL_POP_ERROR`
-- `Z2UI5_CL_POP_FILE_DL`
-- `Z2UI5_CL_POP_FILE_UL`
-- `Z2UI5_CL_POP_GET_RANGE`
-- `Z2UI5_CL_POP_GET_RANGE_M`
-- `Z2UI5_CL_POP_HTML`
-- `Z2UI5_CL_POP_INPUT_VAL`
-- `Z2UI5_CL_POP_ITAB_JSON_DL`
-- `Z2UI5_CL_POP_JS_LOADER`
-- `Z2UI5_CL_POP_MESSAGES`
-- `Z2UI5_CL_POP_PDF`
-- `Z2UI5_CL_POP_TABLE`
-- `Z2UI5_CL_POP_TEXTEDIT`
-- `Z2UI5_CL_POP_TO_CONFIRM`
-- `Z2UI5_CL_POP_TO_INFORM`
-- `Z2UI5_CL_POP_TO_SELECT`
-
-Help expand this collection to cover more cases — contributions are welcome.