Merge pull request #83 from abap2UI5/claude/message-error-sidebar-category-TWXV0

docs(cookbook): restore Message, Error as own sidebar category below UI Interaction

Author: oblomov-dev

docs/.vitepress/config.mjs

@@ -117,17 +117,6 @@ export default defineConfig({
         link: "/development/controller/life_cycle",
         collapsed: true,
         items: [
-          {
-            text: "Controller",
-            link: "/development/controller/life_cycle",
-            collapsed: true,
-            items: [
-              { text: "Life Cycle", link: "/development/controller/life_cycle" },
-              { text: "Init", link: "/development/controller/init" },
-              { text: "Event", link: "/development/controller/event" },
-              { text: "Navigated", link: "/development/controller/navigated" },
-            ],
-          },
           {
             text: "View",
             link: "/development/view/overview",
@@ -160,9 +149,10 @@ export default defineConfig({
           },
           {
             text: "Event, Navigation",
-            link: "/development/events/backend",
+            link: "/development/controller/life_cycle",
             collapsed: true,
             items: [
+              { text: "Life Cycle", link: "/development/controller/life_cycle" },
               { text: "Backend", link: "/development/events/backend" },
               { text: "Frontend", link: "/development/events/frontend" },
               { text: "Follow-up", link: "/development/events/follow_up" },
@@ -215,6 +205,13 @@ export default defineConfig({
               { text: "Title", link: "/development/specific/title" },
               { text: "Timer", link: "/development/specific/timer" },
               { text: "URL Handling", link: "/development/specific/url" },
+            ],
+          },
+          {
+            text: "Message, Error",
+            link: "/development/messages/messages",
+            collapsed: true,
+            items: [
               { text: "Message", link: "/development/messages/messages" },
               { text: "Error", link: "/development/messages/errors" },
               { text: "Logging", link: "/development/messages/logging" },
@@ -244,11 +241,10 @@ export default defineConfig({
               { text: "WebSocket", link: "/development/specific/websocket" },
               { text: "Logout", link: "/configuration/logout" },
               { text: "OData", link: "/development/model/odata" },
-              { text: "App State", link: "/development/navigation/app_state" },
-              { text: "Share, Bookmark", link: "/development/navigation/share" },
+              { text: "App State, Share, Bookmark", link: "/development/navigation/app_state" },
               {
                 text: "Utilities",
-                collapsed: true,
+                collapsed: false,
                 items: [
                   { text: "Value Help", link: "/development/specific/value_help" },
                   { text: "Demo Output", link: "/development/specific/demo_output" },

docs/development/controller/controller.md

@@ -1,9 +1,9 @@
 ---
 outline: [2, 4]
 ---
-# App State
+# App State, Share, Bookmark
 
-abap2UI5 saves the current app state so you can return to it later — like how standard UI5 apps manage state.
+abap2UI5 saves the current app state so you can return to it later — like how standard UI5 apps manage state. This opens up several useful options, like sharing and bookmarking the current state of your app.
 
 ### Usage
 Each state persists as a draft with a unique ID. Calling `client->set_app_state_active` appends this ID as a hash fragment to the URL. The resulting URL is shareable — copy it and open it in another browser window (or send it to a colleague) to restore the same app state. The hash value (`z2ui5-xapp-state=...`) is a server-side key that points to the saved draft. Drafts expire after a configurable time (default: 4 hours, adjustable via [User Exits](/advanced/extensibility/user_exits)).
@@ -47,3 +47,40 @@ ENDCLASS.
 ```
 
 For a complete implementation, see sample `Z2UI5_CL_DEMO_APP_321`.
+
+### Share
+Add a share button that copies the current state to the clipboard to share with colleagues:
+```abap
+CLASS z2ui5_cl_sample_share DEFINITION PUBLIC.
+
+  PUBLIC SECTION.
+    INTERFACES z2ui5_if_app.
+    DATA mv_quantity TYPE string.
+
+ENDCLASS.
+
+CLASS z2ui5_cl_sample_share IMPLEMENTATION.
+  METHOD z2ui5_if_app~main.
+
+    CASE abap_true.
+
+      WHEN client->check_on_navigated( ).
+
+        DATA(view) = z2ui5_cl_xml_view=>factory( )->shell( )->page(
+          )->label( `quantity`
+          )->input( client->_bind_edit( mv_quantity )
+          )->button( text  = `share` press = client->_event( `BUTTON_POST` ) ).
+        client->view_display( view->stringify( ) ).
+
+      WHEN client->check_on_event( `BUTTON_POST` ).
+
+        client->follow_up_action( client->_event_client( z2ui5_if_client=>cs_event-CLIPBOARD_APP_STATE ) ).
+        client->message_toast_display( `clipboard copied` ).
+
+    ENDCASE.
+  ENDMETHOD.
+ENDCLASS.
+```
+
+### Bookmark
+You can also use these URLs for bookmarking, but note that the server keeps the app state only for a limited time. The default is 4 hours. See the [draft service](https://github.com/abap2UI5/abap2UI5/blob/main/src/01/01/z2ui5_cl_core_srv_draft.clas.abap#L46) source.

docs/development/controller/event.md

@@ -44,7 +44,7 @@ ENDCLASS.
 
 #### Copy the App State URL
 
-To share the current app state instead of a custom string, use `clipboard_app_state` — see [Share, Bookmark](../navigation/share.md).
+To share the current app state instead of a custom string, use `clipboard_app_state` — see [App State, Share, Bookmark](../navigation/app_state.md).
 
 ::: warning
 The browser's Clipboard API requires HTTPS (or `localhost`). On plain HTTP the call is silently ignored.

docs/development/controller/init.md

@@ -6,7 +6,7 @@ outline: [2, 4]
 With abap2UI5 up and running, here are a few directions to take.
 
 #### Development
-Learn how to build views, handle events, share data, and work with tables. The development guide covers what you need for everyday work. Start with the [Development guide](/development/controller/controller).
+Learn how to build views, handle events, share data, and work with tables. The development guide covers what you need for everyday work. Start with the [Development guide](/development/controller/life_cycle).
 
 #### Configuration
 Getting ready for production? The configuration guides walk through security, performance tuning, Launchpad integration, and more. Start with the [Configuration guide](/configuration/setup).