How hbroek/reken works
Main Components
a) Core Engine Components:
• Setup Controller
• Runtime Controller
• Event Management System
• DOM Update Engine
• REST Service Handler
• Component System
• Routing System
b) Integration Layer:
• HTML Attribute Parser
• Template Engine
• Data Binding System
c) External Interfaces:
• REST API Integration
• File System Integration
• Browser DOM Interface
┌─────────────────────────────────────────────────────────┐
• HTML Application Layer │
• (Custom attributes, Components, Templates, Includes) │
• ┤
• Reken Core Engine │
• ┬──────────────────────┬──────────────────┤
• Setup │Runtime │Event │
• Controller │Controller │Management │
• ┴──────────────────────┴──────────────────┤
• Integration Layer │
• ┬──────────────────────┬──────────────────┤
• Attribute │Template │Data │
• Parser │Engine │Binding │
• ┴──────────────────────┴──────────────────┤
• External Interfaces │
• (REST API, File System, Browser DOM) │
• ┘
Key Relationships
a) Data Flow:
• HTML Attributes → Attribute Parser → Setup/Runtime Controllers
• User Events → Event Management → Runtime Controller
• REST Calls → REST Service Handler → Data Binding System
• Component Templates → Template Engine → DOM Update Engine
b) Control Flow:
• Setup Controller → Event Management (one-time setup)
• Runtime Controller → DOM Update Engine (continuous updates)
• Component System → Template Engine (component rendering)
Implementation Details
• Single DOM tree architecture
• Direct DOM manipulation without Virtual DOM
• Event-driven update system
• Component reusability
• HTML-first approach
Remember to include notes about the ES6 dependency and browser compatibility constraints, as these are important architectural considerations.