oca-pos/odoo-bringout-oca-pos-pos_edit_order_line/doc/ARCHITECTURE.md
Ernad Husremovic 377f346a99 Move all OCA POS modules from oca-technical to dedicated oca-pos submodule
Reorganized 74 POS-related modules for better structure:
- Moved all odoo-bringout-oca-pos-* packages from packages/oca-technical/
- Now organized in dedicated packages/oca-pos/ submodule
- Includes payment, receipt, loyalty, order, product, and partner modules
- Maintains all module functionality while improving project organization

This creates a cleaner separation between general technical modules
and Point of Sale specific functionality.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-08-30 17:15:35 +02:00

835 B
Raw Blame History

Architecture

flowchart TD
    U[Users] -->|HTTP| V[Views and QWeb Templates]
    V --> C[Controllers]
    V --> W[Wizards  Transient Models]
    C --> M[Models and ORM]
    W --> M
    M --> R[Reports]
    DX[Data XML] --> M
    S[Security  ACLs and Groups] -. enforces .-> M

    subgraph Pos_edit_order_line Module - pos_edit_order_line
      direction LR
      M:::layer
      W:::layer
      C:::layer
      V:::layer
      R:::layer
      S:::layer
      DX:::layer
    end

    classDef layer fill:#eef8ff,stroke:#6ea8fe,stroke-width:1px

Notes

  • Views include tree/form/kanban templates and report templates.
  • Controllers provide website/portal routes when present.
  • Wizards are UI flows implemented with models.TransientModel.
  • Data XML loads data/demo records; Security defines groups and access.