How lucasjunqueira-var/tilbuci works
Main System Components
a) Client-Side Applications
• Editor Application (Haxe-based)
• Player Component
• Multiple Runtime Environments (Desktop, Mobile, PWA, Website)
b) Server-Side Infrastructure
• Web Services Layer
• Media Management
• User Management
• Database Layer
Key Architectural Elements to Highlight
a) Frontend Architecture:
• Main components under app/Source/com/tilbuci:
• Editor (core editing functionality)
• Player (runtime player)
• UI Components (extensive UI system)
• Components (various media types)
• Plugin System
• Script Engine
b) Backend Architecture:
• Web Services (server/app/WS* files)
• Core Services (Movie, Scene, Media management)
• Data Storage
• Export Systems (Desktop, Cordova, PWA, Website)
[Client Layer]
• Editor Interface
• UI Components
• Media Handlers
• Script Engine
• Player Runtime
• Display Engine
• Plugin System
• Contraptions
• Export Targets
• Desktop
• PWA
• Website
• Cordova
[Server Layer]
• Web Services API
• User Management
• Media Services
• Movie Management
• Scene Management
• Core Services
• File Management
• Export Services
• Analytics
• Data Storage
Important Relationships
• Data flow between Editor and Server
• Plugin integration points
• Media asset flow
• Runtime deployment paths
• User interaction flows
Technical Details
Annotations for:
• Haxe compilation targets
• PHP backend services
• Database schema references
• Export format specifications
• Plugin API endpoints
• User Interface Layer
• Business Logic Layer
• Data Access Layer
• Runtime Environments
• External Services
This structure will help other developers understand both the high-level architecture and the detailed component interactions while maintaining clarity about the system's capabilities and constraints.