How john-ds/express-apps works
Project type and purpose
• This is a desktop-only suite of four WPF (Windows Presentation Foundation) applications plus a shared control library:
• Type Express (rich text editor)
• Present Express (slideshow maker)
• Font Express (font organiser)
• Quota Express (storage analysis)
• ExpressControls (custom WPF controls, styles, themes, resources)
File structure
• Top-level solution (.sln) that groups five projects.
• “ExpressControls” is a class library containing reusable XAML controls, themes, resources, sounds, etc.
• Four application projects each include:
• App.xaml / App.xaml.cs (application bootstrap)
• MainWindow.xaml/ .cs (UI entry point)
• Options/Settings (Settings.settings + user preferences)
• All use local file system for storing user data and configuration.
README
• Confirms the suite purpose: a collection of quality WPF apps, each optimised for a specific task.
• No server or cloud back-end—desktop-only, with occasional “integration” points (Dropbox, ffmpeg calls).
a. Main components
• User Workstation (Windows)
• Four WPF Applications (TypeExpress, PresentExpress, FontExpress, QuotaExpress)
• Shared Control Library (ExpressControls.dll)
• Local Data Stores (app settings, user files, fonts folder, export folder)
• External Tools & Services
• ffmpeg suite (video encoding/decoding)
• FontReg.exe (font registration)
• Dropbox integration pages (dropbox-index.html)
b. Relationships & interactions
• Each WPF app depends on ExpressControls.
• UI Layer (XAML + code-behind or MVVM ViewModels) calls into Controls Library for custom widgets.
• Business Logic in each app reads/writes local storage (settings, documents, fonts, media).
• When multimedia tasks arise (slideshow export, font install), apps invoke external executables (ffmpeg, FontReg).
• Dropbox integration is exposed via embedded browser control pointing to local HTML pages.
c. Architectural patterns & design principles
• MVVM (Model-View-ViewModel) for each WPF app
• Layered separation:
• Presentation (Views, custom controls)
• ViewModels (application logic, command bindings)
• Models (file-based data structures, exportable classes)
• Reusability: ExpressControls library isolates all UI components, styles, themes.
• Convention-based configuration (Settings.settings, App.config).
d. Key technologies
• .NET Framework WPF, XAML, C#
• Third-party tools: ffmpeg suite, FontReg
• Local file I/O, Settings API, Embedded resources (XAML resource dictionaries, sound files)
Final advice
• Be exhaustive: include all projects, all major resource folders, all external tool interactions.
• Special integration (Dropbox HTML pages, multimedia pipeline).
• MVVM triad within each app if deeper detail is needed.