How fliegendewurst/triliumdroid works
Main Components Identification
The system should be represented with these primary components:
a) Client-Side Components:
• UI Layer (Activities and Fragments)
• Data Management Layer
• Sync Service Layer
• Storage Layer
b) External Components:
• Trilium Notes Server
• Android System Services
• External Apps (for sharing)
Detailed Component Breakdown
A. UI Layer (Top Level):
• WelcomeActivity
• MainActivity
• SetupActivity
• AboutActivity
• Fragments hierarchy:
• NoteTreeFragment
• NoteEditFragment
• NoteMapFragment
• NoteRelatedFragment
B. Data Management Layer (Middle Level):
• Model Classes:
• Note
• Attribute
• Branch
• Relation
• Cache Management
• Data Synchronization
C. Backend Communication Layer:
• FrontendBackendApi
• ConnectionUtil
• Sync Protocol Handlers
D. Storage Layer (Bottom Level):
• SQLite Database (schema.sql)
• File Provider
• Cache Storage
Relationships and Data Flow
• User interaction flow
• Data synchronization flow
• Storage operations flow
Specific Implementation Details
• The sync protocol support for versions 0.90.12 and 0.63.7
• Tree structure and navigation
• Attribute inheritance system
• Local/global note mapping
• Basic scripting support
Technical Specifications
• Kotlin as primary language
• Android 8.0+ support
• External dependencies (AztecEditor, etc.)
• Database schema version