tom4711/easyredminetool

Purpose and runtime

EasyRedmineTool is a cross-platform .NET 10 desktop client for Redmine/Easy Redmine. It manages tickets, creates time entries, stores favorites, plans recurring bookings, and summarizes weekly hours. Avalonia 12 provides the macOS, Windows, and Linux UI; Redmine’s REST API is the only stated external service.

Entry point and composition

The application starts in src/EasyRedmineTool.Desktop/Program.cs, initializes Avalonia through src/EasyRedmineTool.Desktop/App.axaml, and registers the object graph in src/EasyRedmineTool.Desktop/DependencyInjection/ServiceCollectionExtensions.cs. Desktop-specific composition owns shell navigation and platform presentation; reusable business/UI state lives in Core.

Desktop shell and presentation boundary

src/EasyRedmineTool.Desktop/Views/MainWindow.axaml hosts the feature views, coordinated by src/EasyRedmineTool.Desktop/ViewModels/MainWindowViewModel.cs. Feature screens bind Core view models for ticket list, time entries, weekly summary, settings, and series booking. Avalonia views should remain presentation adapters, rather than owning API or persistence behavior.

Core MVVM application layer

Core view models orchestrate user actions and expose bindable state: src/EasyRedmineTool.Core/ViewModels/TicketListViewModel.cs, src/EasyRedmineTool.Core/ViewModels/TimeEntriesViewModel.cs, and src/EasyRedmineTool.Core/ViewModels/WeeklySummaryViewModel.cs. They depend on service interfaces, translate service results into rows/form state, and connect flows such as selecting a ticket from the summary to time entry creation.

Redmine integration and service boundary

src/EasyRedmineTool.Core/Api/EasyRedmineApiClient.cs is the HTTP/JSON boundary to Redmine, behind src/EasyRedmineTool.Core/Api/IEasyRedmineApiClient.cs; API failures are represented by src/EasyRedmineTool.Core/Api/RedmineApiException.cs. Domain services encapsulate workflows: src/EasyRedmineTool.Core/Services/TicketService.cs loads and merges ticket data, while src/EasyRedmineTool.Core/Services/TimeEntryService.cs loads activities/entries and submits creates or updates. API DTOs and request/response models isolate Redmine payload shape from UI state.

Local settings, cache, and connection flow

src/EasyRedmineTool.Core/Services/AppSettingsService.cs persists base URL, API key, theme, cached tickets, favorites, and last-entry defaults in the per-user settings file. src/EasyRedmineTool.Core/Services/ConnectionTestService.cs validates configured credentials through the API boundary. Credentials are intentionally local but unencrypted; no secrets belong in repository state.

Planning and reporting transformations

Recurring booking intent is expanded into dated preview/actions by src/EasyRedmineTool.Core/SeriesBookingPlanner.cs, consumed through src/EasyRedmineTool.Core/ViewModels/SeriesBookingViewModel.cs. Loaded time entries are aggregated into quarterly calendar-week and ticket totals by src/EasyRedmineTool.Core/WeeklySummaryBuilder.cs. These are deterministic domain transformations separate from HTTP and Avalonia rendering.

Delivery

The solution is EasyRedmineTool.slnx; GitHub Actions in .github/workflows/release.yml produces self-contained platform artifacts and GitHub Releases. The app targets Windows x64, macOS x64/ARM64, and Linux x64/ARM64.