How mrmlik12/note-shr works
Main Components
• Core Business Logic: This is primarily contained in the NoteSHR.Core project, which holds the models, converters, services, and view model base classes. It encapsulates the “brain” of the application including data definitions, persistence interfaces (IDataPersistence), and business domain logic (e.g., working with boards, notes, and nodes).
• Platform-Specific Frontends:
– Desktop: Represented by the NoteSHR.Desktop project.
– Browser/Web: Represented by the NoteSHR.Browser project which also contains assets (HTML, CSS, and JS files in the AppBundle folder).
– Mobile: Separate projects for NoteSHR.Android and NoteSHR.iOS.
• File Handling & Data Persistence: The NoteSHR.File project handles import/export operations, conversion of board files, and may interact with persistence mechanisms. Include services and utilities related to the file system (e.g., BoardConverter, BoardExporter, BoardImporter, PathUtils).
• Build & Test Infrastructure: Although not part of runtime architecture, the build directory (along with NUKE build scripts) and test projects (under test/NoteSHR.File.Tests) help automate and validate the project build and behaviors.
Relationships and Interactions
• All UI frontends (Desktop, Browser, Android, iOS) should be shown as separate client components that interact with the common business logic.
• The shared business logic (in NoteSHR.Core) drives the overall application state, and is consumed by the MVVM implementation in the main NoteSHR UI project.
• File operations managed by NoteSHR.File provide persistence capabilities across these platforms—link this module to both the Core and the UI components which trigger import/export features.
Architectural Patterns and Design Principles
• MVVM Pattern: Emphasize how the separation of View (UI components) and ViewModel (in the shared NoteSHR project and NoteSHR.Core) helps maintain platform agnosticism.
• Layered Architecture: Visually differentiate the presentation layer (views/controls), the business logic layer (models/services in NoteSHR.Core), and the persistence/file handling layer (NoteSHR.File). This separation enhances maintainability and allows for parallel development on various fronts.
• Cross-Platform Code Sharing: Highlight that despite having different platform projects, most business logic and UI logic (especially ViewModels) are shared—helping reduce code duplication.
Incorporate Technologies and Frameworks
• The build system (NUKE) should be noted as part of the CI/CD pipeline, since it integrates build, test, and publish workflows.