Reorganize frontend events and simplify view binding documentation

[oblomov-dev]

Summary

This PR reorganizes the frontend events documentation with improved categorization and adds comprehensive documentation for control method invocation. It also simplifies the view binding API by removing the now-obsolete view parameter from _bind() calls and clarifying the single unified model architecture.

Key Changes

Documentation Reorganization

• Frontend events (docs/cookbook/event_navigation/frontend.md):

  • Reorganized event constants into logical groups: Framework, Actions, and Control calls
  • Added new section "Calling control methods on the frontend" explaining control_by_id, control_global, and binding_call events
  • Documented positional argument handling for control method calls
  • Added table clarifying which events accept which arguments
  • Documented the view parameter for scoping control lookups to specific views (popup, popover, nested, etc.)
  • Included migration note about the view parameter moving from t_arg to a dedicated importing parameter

• Nested views (docs/cookbook/view/nested_views.md):

  • Removed view parameter from all client->_bind() calls (now defaults to main view)
  • Renamed section from "Routing Bindings to the Right View" to "Refreshing the Right View"
  • Clarified that all bound data lives in a single unified client-side model regardless of view
  • Added table showing which refresh method to call for each view type (main, nested, nested 2nd)
  • Added deprecation note explaining that the view parameter is now inert and kept only for backward compatibility

• Follow-up actions (docs/cookbook/expert_more/follow_up_action.md):

  • Added new section "Calling a control method" with examples of using control events in follow_up_action()
  • Documented the view parameter for scoping control lookups in follow-up actions

• XML templating (docs/cookbook/view/xml_templating.md):

  • Minor text correction (incomplete line fix)

Notable Implementation Details

• The changes maintain full backward compatibility — code passing the view parameter to _bind() continues to work
• The unified model architecture simplifies data management while the view-specific refresh methods (view_model_update(), nest_view_model_update(), etc.) control which rendered view receives updates
• Control method invocation uses positional arguments with empty slots represented as `` to maintain argument positions

https://claude.ai/code/session_01NjYGeMm8yvpJhavp6hdGyN