- Replace the Python/Docker setup with a Rust workspace and Tauri frontend - Add core crates for archive, audio, MIDI, plugin, and desktop UI layers - Refresh the app scaffolding, build config, and documentation
29 lines
1.3 KiB
Markdown
29 lines
1.3 KiB
Markdown
# Fbrowser
|
|
|
|
Fbrowser is being migrated from a Python/PyQt desktop app to a Rust + Tauri + React desktop application.
|
|
|
|
## Repository Layout
|
|
|
|
- `src/`: React frontend for the new desktop app.
|
|
- `src-tauri/`: Tauri host application and IPC command layer.
|
|
- `crates/`: Shared Rust workspace crates for catalog, audio, MIDI, archives, and future plugin-facing APIs.
|
|
- `migrations/`: SQLite schema migrations for the new local catalog.
|
|
- `python-src/`: Legacy Python implementation kept as a feature reference during migration.
|
|
|
|
## Current Status
|
|
|
|
- The new Tauri/Rust/React application builds successfully.
|
|
- The legacy Python code has been moved out of the repository root to keep the migration boundary clear.
|
|
- The desktop shell, catalog model, scan pipeline, archive utilities, timer, waveform generation, and transport scaffolding are in place.
|
|
- Some areas are still scaffold-level rather than production-complete, especially MIDI playback internals and broader archive-format support.
|
|
|
|
## Verification
|
|
|
|
- Frontend production build: `npm run build`
|
|
- Rust workspace checks/tests: `cargo check --manifest-path src-tauri/Cargo.toml` and `cargo test --workspace`
|
|
|
|
## Notes
|
|
|
|
- The Python code under `python-src/` is no longer the primary application entrypoint.
|
|
- The new root-level app is the active migration target.
|