How bloombooks/bloomdesktop works
Main Components Overview
a) Frontend Layer:
• React-based UI components (BloomBrowserUI directory)
• Web views for document editing
• Browser-based tools and editors
• Style and theme management
b) Backend Layer:
• C# WinForms application (BloomExe directory)
• WebView2 PDF maker component
• File system management
• Book processing engine
c) External Services:
• Crowdin integration for localization
• TeamCity build system
• YouTrack for issue tracking
• S3 for storage
• BloomLibrary.org integration
Key Architectural Patterns to Highlight
a) Hybrid Architecture:
• Bridge between C# backend and web frontend
• WebSocket communication channels
• API controllers for frontend-backend interaction
b) Book Processing Pipeline:
• Template system
• Content processing
• PDF generation
• Export formats (ePub, PDF, BloomPub)
c) Plugin System:
• XMatter templates
• Branding packages
• Custom templates
Data Flow Representation
• User input → UI components → Backend processing
• Template selection → Book creation → Output generation
• File system operations
• External service interactions
Component Details
a) Frontend Components:
• Page editors
• Toolbox
• Collection management
• Publishing tools
• Style editors
b) Backend Services:
• Book storage
• Image processing
• Font management
• PDF generation
• File compression
c) Integration Points:
• URL handlers (bloom:// protocol)
• External tool integration
• Cloud services connection
Important Subsystems
Specialized subsystems:
• Localization management
• Template processing
• Book compilation
• Publishing pipeline
• Team collection features
Development Environment
A section showing:
• Build pipeline
• Development tools
• Testing framework
• Continuous integration