How pezfisk/oxidemanager works
Project Type and Purpose
• This is a desktop GUI tool written in Rust with a Slint-based front end.
• Purpose: help users extract game mod archives (.zip, .rar, .7z) from a source folder, place (via symlink or copy) the extracted files into a target game directory, and manage mod “profiles” (source/target pairs, optional SteamGridDB images).
a. User Interface Layer (Slint)
• ui/*.slint files define windows, dialogs, grid view, profile editor, profile images, profile state.
b. Application Core (Rust)
• src/main.rs – application entry point, Slint event bindings
• src/profile_manager.rs – handles loading/saving profiles, reading .env for SteamGridDB API key, fetching profile images via HTTP
• src/extract.rs – scans source directory, identifies archives, invokes decompression logic (via Rust crates or external tools) into .temp/
• src/file_manager.rs – moves or symlinks files from .temp/ to target game directory, applies overwrite/direct-extract options
c. File System
• User’s source directory (compressed mods)
• Temporary directory (.temp/)
• Target game directory (where mods are “installed”)
• Local config/profile storage (e.g., file in user’s home folder)
d. External Service
• SteamGridDB REST API (optional; used by profile_manager.rs to fetch thumbnails)
• build.rs / .cargo/config.toml / build.sh – compile-time selection of Slint backend and style
• .env file – injection of STEAMGRIDDB_API_KEY
Relationships and Data Flows
• User clicks buttons in the Slint UI → events propagate to main.rs.
• main.rs calls profile_manager to load/save profile metadata, triggers image fetch from SteamGridDB.
• On “Extract” action:
• UI → calls extract.rs, which scans source dir for archives → writes to .temp/.
• Once extraction completes, main.rs invokes file_manager.rs.
• file_manager moves or symlinks files from .temp/ → target game directory, respecting overwrite/direct flags.
• Status updates (progress, errors) flow back to the UI for display.
Architectural Patterns & Design Principles
• Separation of Concerns: UI (Slint) vs. business logic (Rust modules).
• Event-Driven Flow: Slint events trigger Rust functions; core modules emit status events back to UI.
• Modular Design: Each Rust file (extract, file_manager, profile_manager) encapsulates a single responsibility.
• Safety and Performance: Use of symlinks to minimize disk usage, optional direct extraction mode.
Technologies & Frameworks to Annotate
• Frontend: Slint (UI definitions in .slint files).
• Language: Rust, Cargo.
• Decompression: Rust crates for ZIP/RAR/7z or system utilities.
• HTTP Client: (e.g., reqwest) for SteamGridDB.
• Environment: dotenv for API key.
• Build Configuration: build.rs, .cargo/config.toml.