Merge pull request #118 from abap2UI5/claude/docs-gaps-improvements-5kabp7

docs: fix stale references and document missing client API methods

Author: oblomov-dev

docs/advanced/agent.md

@@ -177,7 +177,7 @@ Browse them online (no system needed): <https://abap2ui5.github.io/web-abap2ui5-
 
 Before building a custom dialog, check whether one of the built-in popup classes already covers the case:
 
-`Z2UI5_CL_POP_TO_CONFIRM`, `Z2UI5_CL_POP_TO_INFORM`, `Z2UI5_CL_POP_TO_SELECT`, `Z2UI5_CL_POP_FILE_UL`, `Z2UI5_CL_POP_FILE_DL`, `Z2UI5_CL_POP_TABLE`, `Z2UI5_CL_POP_TEXTEDIT`, `Z2UI5_CL_POP_PDF`, `Z2UI5_CL_POP_HTML`, `Z2UI5_CL_POP_MESSAGES`, `Z2UI5_CL_POP_ERROR`, `Z2UI5_CL_POP_GET_RANGE`, `Z2UI5_CL_POP_GET_RANGE_M`, `Z2UI5_CL_POP_INPUT_VAL`, `Z2UI5_CL_POP_JS_LOADER`, `Z2UI5_CL_POP_ITAB_JSON_DL`
+`Z2UI5_CL_POP_TO_CONFIRM`, `Z2UI5_CL_POP_TO_INFORM`, `Z2UI5_CL_POP_TO_SELECT`, `Z2UI5_CL_POP_FILE_UL`, `Z2UI5_CL_POP_FILE_DL`, `Z2UI5_CL_POP_TABLE`, `Z2UI5_CL_POP_DATA`, `Z2UI5_CL_POP_TEXTEDIT`, `Z2UI5_CL_POP_PDF`, `Z2UI5_CL_POP_HTML`, `Z2UI5_CL_POP_IMAGE_EDITOR`, `Z2UI5_CL_POP_MESSAGES`, `Z2UI5_CL_POP_BAL`, `Z2UI5_CL_POP_ERROR`, `Z2UI5_CL_POP_GET_RANGE`, `Z2UI5_CL_POP_GET_RANGE_M`, `Z2UI5_CL_POP_INPUT_VAL`, `Z2UI5_CL_POP_JS_LOADER`, `Z2UI5_CL_POP_DEMO_OUTPUT`
 
 → [Built-in popups](/cookbook/popup_popover/built_in)
 

docs/configuration/troubleshooting.md

@@ -2,7 +2,7 @@
 outline: [2, 4]
 ---
 # Debugging
-Since all logic runs in ABAP, you can debug everything in the ABAP environment. Set an external breakpoint, because HTTP calls abap2UI5 apps externally.
+Since all logic runs in ABAP, you can debug everything in the ABAP environment. Set an external breakpoint, because abap2UI5 apps are called externally via HTTP.
 
 ### Backend
 Set a breakpoint in your abap2UI5 app to debug the code. Check that the XML view builds correctly and that all events fire on the backend as expected.

docs/cookbook/browser_interaction/url_handling.md

@@ -22,4 +22,16 @@ client->action->gen(
 ```
 
 ### Browser History
-To control browser history, see sample `Z2UI5_CL_DEMO_APP_139`.
+Two client methods control the browser history from the backend:
+
+Push a new history entry — the value is appended to the URL hash, so app state becomes bookmarkable and the browser back button steps through your pushed states:
+```abap
+client->set_push_state( `&my-app-state=detail` ).
+```
+
+Trigger a browser back navigation (`history.back()`) with the next response:
+```abap
+client->set_nav_back( ).
+```
+
+For a complete example, see sample `Z2UI5_CL_DEMO_APP_139`.

docs/cookbook/popup_popover/built_in.md

@@ -3,23 +3,28 @@ outline: [2, 4]
 ---
 # Built-In
 
-A few pre-built popup classes cover the most common cases:
+Pre-built popup classes cover the most common cases. Call them via [navigation](/cookbook/event_navigation/navigation) — `client->nav_app_call( ... )` — and read the result back with `client->get_app_prev( )` when your app regains control:
 
-- `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`
+| Class | Purpose |
+| --- | --- |
+| `Z2UI5_CL_POP_TO_CONFIRM` | Confirmation dialog with confirm/cancel events |
+| `Z2UI5_CL_POP_TO_INFORM` | Information message dialog |
+| `Z2UI5_CL_POP_TO_SELECT` | Select one or more entries from an internal table |
+| `Z2UI5_CL_POP_TABLE` | Display an internal table |
+| `Z2UI5_CL_POP_DATA` | Display any data object (structure or table) |
+| `Z2UI5_CL_POP_TEXTEDIT` | Multi-line text editor |
+| `Z2UI5_CL_POP_INPUT_VAL` | Prompt the user for a single input value |
+| `Z2UI5_CL_POP_GET_RANGE` | Maintain range / select-option criteria |
+| `Z2UI5_CL_POP_GET_RANGE_M` | Maintain multiple ranges at once |
+| `Z2UI5_CL_POP_FILE_UL` | File upload |
+| `Z2UI5_CL_POP_FILE_DL` | File download |
+| `Z2UI5_CL_POP_PDF` | PDF preview |
+| `Z2UI5_CL_POP_HTML` | Display HTML content |
+| `Z2UI5_CL_POP_IMAGE_EDITOR` | Edit an image (crop, resize, filter) |
+| `Z2UI5_CL_POP_MESSAGES` | Display a message table |
+| `Z2UI5_CL_POP_BAL` | Display a Business Application Log (BAL) |
+| `Z2UI5_CL_POP_ERROR` | Error display |
+| `Z2UI5_CL_POP_JS_LOADER` | Load custom JavaScript libraries |
+| `Z2UI5_CL_POP_DEMO_OUTPUT` | Quick demo-style output of arbitrary data |
 
 Help expand this collection to cover more cases — contributions are welcome.

docs/cookbook/popup_popover/popover.md

@@ -39,3 +39,5 @@ To show a popover, call `client->popover_display` and pass the ID of the control
 
   ENDMETHOD.
 ```
+
+Like popups, popovers support a data-only refresh: `popover_model_update( )` pushes changed ABAP values into the open popover without re-rendering its XML.

docs/cookbook/popup_popover/popup.md

@@ -53,6 +53,8 @@ A typical popup flow shows a normal view, opens a popup, and finally closes it.
   ENDMETHOD.
 ```
 
+The popup has the same lifecycle trio as the main view: `popup_display( )` renders the XML, `popup_model_update( )` pushes changed ABAP data into the **already-rendered** popup without re-rendering it, and `popup_destroy( )` closes it.
+
 ## Separated App
 For a cleaner source layout, encapsulate popups in separate classes and call them via [navigation](/cookbook/event_navigation/navigation).
 

docs/cookbook/view/nested_views.md

@@ -78,8 +78,9 @@ The whole point of nested views is to re-render only what changed. Three calls c
 | `client->view_display( ... )`     | Replaces the main view's XML. The anchor is recreated, so any nested content is lost too.    |
 | `client->nest_view_display( ... )`| Replaces only the nested view. The main view stays on screen.                                |
 | `client->nest_view_model_update( )` | Pushes current ABAP data values into the **already-rendered** nested view. No re-render.   |
+| `client->nest_view_destroy( )`    | Removes the nested view from the frontend without touching the main view.                    |
 
-The matching call for the main view is `client->view_model_update( )` — push data changes into the rendered main view without re-rendering it.
+The matching calls for the main view are `client->view_model_update( )` — push data changes into the rendered main view without re-rendering it — and `client->view_destroy( )`. The second nested slot has the same trio: `nest2_view_display( )`, `nest2_view_model_update( )` and `nest2_view_destroy( )`.
 
 A rule of thumb:
 

docs/get_started/about.md

@@ -99,7 +99,7 @@ Getting started is easy:
 2. Set up an HTTP service for browser communication
 3. Start building!
 
-→ *See the [Installation Guide](/get_started/quickstart) for full instructions*
+→ *See the [Quickstart Guide](/get_started/quickstart) for full instructions*
 
 ### Community
 <br>

docs/get_started/hello_world.md

@@ -30,7 +30,7 @@ abap2UI5 follows a thin-frontend model: the browser only renders UI5 views, whil
 - **State lives in your class.** Public attributes of your app class hold data between roundtrips; abap2UI5 serializes and restores them for you, so you don't manage sessions manually.
 - **The `client` object is your only API.** Use it to display views, check which event fired, bind attributes to UI5 controls, and trigger navigation.
 
-Every abap2UI5 app implements the `z2ui5_if_app` interface. It has a single method, `main`, with one parameter: `client` of type `z2ui5_if_client`:
+Every abap2UI5 app implements the `z2ui5_if_app` interface. It has a single method, `main`, with one parameter: `client` of type `z2ui5_if_client` (simplified — the interface also carries a few framework-managed attributes you normally never touch):
 ```abap
 INTERFACE z2ui5_if_app PUBLIC.
   METHODS main
@@ -95,15 +95,15 @@ ENDCLASS.
 The framework calls `main` on every roundtrip — on initialization and after every user interaction (button press, input submit, etc.):
 
 ```text
-┌─────────┐       ┌──────────┐       ┌─────────┐
+┌──────────┐       ┌──────────┐       ┌──────────┐
 │ Browser  │──────>│  main()  │──────>│ Browser  │
 │ (Start)  │  HTTP │  init    │  HTTP │ (View)   │
-└─────────┘       └──────────┘       └────┬─────┘
-                                          │ user clicks
-┌─────────┐       ┌──────────┐       ┌────┴─────┐
+└──────────┘       └──────────┘       └────┬─────┘
+                                           │ user clicks
+┌──────────┐       ┌──────────┐       ┌────┴─────┐
 │ Browser  │<──────│  main()  │<──────│ Browser  │
 │ (Update) │  HTTP │  event   │  HTTP │ (Event)  │
-└─────────┘       └──────────┘       └──────────┘
+└──────────┘       └──────────┘       └──────────┘
 ```
 
 Use the lifecycle checks to tell these phases apart:

docs/get_started/quickstart.md

@@ -62,7 +62,7 @@ abap2UI5 talks only to the HTTP service you define, giving you full control over
 
 ### 3. First Launch
 Open the HTTP endpoint in your browser:
-<img width="800" alt="Press `check` and launch the test app. That's it — you can now build your own abap2UI5 apps." src="https://github.com/user-attachments/assets/c8962298-068d-4efb-a853-c44a9b9cda56">
+<img width="800" alt="abap2UI5 startup page with check button and test app launcher" src="https://github.com/user-attachments/assets/c8962298-068d-4efb-a853-c44a9b9cda56">
 Press `check` and launch the test app. That's it — you can now build your own abap2UI5 apps.
 
 ### 4. Your First App