How duinoapp/duinoapp-client-dingo works
Main Application Structure
a) Frontend Layer (Client-Side)
• Code Editor System (components/code)
• File Management System (components/directory-area)
• Terminal Interface (components/terminal)
• Project Management (components/projects)
• Board Management (components/boards)
• Settings & Configuration (components/settings-area)
b) Core Services Layer (Composables)
• Project Service
• Compiler Service
• Serial Communication
• File Actions
• Search Service
• Terminal Management
• Library Management
c) Backend Integration Layer
• Connections to:
• Serial Port Communication
• File System Access
• Build/Compile Services
Component Relationships
a) User Interface Components → Composables
• How UI components interact with services
• Data flow
• Event triggers
• State updates
b) Composables → Backend Services
• How services interact with backend systems
• Async operations
Key Subsystems
a) Editor System
• Monaco Editor Integration
• File Editor
• Rich Text Editor
• Media Viewer
b) Project Management
• Project Settings
• Template Management
• Export/Import
• File Structure
c) Communication Layer
• Serial Communication
• Server Management
• Terminal Interface
• Monitoring Tools
State Management
State flow:
• How composables manage application state
• Shared state between components
• Persistent storage points
External Integrations
Connections to:
• GitHub
• Discord
• Serial Ports
• File System
• Blue: Core UI Components
• Green: Services/Composables
• Orange: External Services
• Purple: State Management
• Gray: Infrastructure Components
Important Architectural Notes:
How the Monaco editor integrates with the rest of the system
• Double lines: API boundaries
• Hexagons: External services
• Rectangles: Internal components
• Clouds: External systems