// ZPWR-FILE-BROWSER — SHARED MULTI-PANE FILE BROWSER

Four hosts, one component

The front end calls the same invoke names everywhere; only the host-side backend differs.

Rust core (crate/)

crate/ (package zpwr-file-browser) holds the filesystem logic faithfully ported from Audio-Haxor: 34 pure pub async fn filesystem functions with no Tauri types, so the crate is usable in any context. Enable the tauri cargo feature to also compile zpwr_file_browser::commands — 35 thin #[tauri::command] wrappers (one per pure fn, plus fb_watcher_set), each named with the exact invoke name the front end calls. The features are additive: a plain cargo build (no features) keeps the crate Tauri-free. For non-Tauri (JUCE) hosts, the capi feature compiles zpwr_file_browser::ffi — a staticlib C ABI whose single entry fb_invoke(cmd, args_json) dispatches by name into the same pure fns and returns a JSON envelope.

zpwr-file-browser = { path = "…/zpwr-file-browser/crate", features = ["tauri"] }

.manage(zpwr_file_browser::commands::watcher_state())
.invoke_handler(tauri::generate_handler![
    zpwr_file_browser::commands::fs_list_dir,
    zpwr_file_browser::commands::fs_copy_path,
    zpwr_file_browser::commands::fb_watcher_set,
    // … all the rest
])

Directory watcher

The crate also bundles the File Browser directory watcher, faithfully ported from Audio-Haxor's fb_watcher.rs: zpwr_file_browser::fb_watcher::WatcherSession is a framework-agnostic, notify-based, non-recursive, 300 ms-debounced single-directory watcher. session.watch(dir, on_change) canonicalizes dir, starts the watch, fires on_change(canonical) on each debounced change, and returns the canonical path; session.stop() tears down. Under the tauri feature, commands::fb_watcher_set wires that callback to AppHandle::emit("file-browser-change", { "dir": canonical }) — the exact event and payload the front end consumes; construct the managed state with commands::watcher_state().

Front end features

Backend contract (each host implements)

The front end calls these on the host IPC object (window.zfbHost.*). A host using a different IPC object can alias it: window.zfbHost = myBackend. Every method returns a Promise. A host that does not support an optional capability should resolve to an empty/neutral value (not throw) so the row or preview degrades gracefully.

Host UI utilities (globals the front end expects)

The front end uses these as globals; the host must define them (most apps already have them):

Mounting

Tauri hosts sync these assets into their served frontend/ via a copy script (copy-file-browser.mjs, mirroring copy-embed-terminal.mjs); JUCE hosts embed them via juce_add_binary_data and serve by basename.

Layout

The GUI stack

zpwr-file-browser is a shared component of the MenkeTechnologies GUI applications. Browse the rest via the MenkeTechnologiesMeta umbrella repo:

• Audio-Haxor — Tauri v2 desktop app; the file browser was extracted from here
• traderview — Tauri v2 market / charting app
• ztranslator — Tauri v2 translation / protocol-bridge app
• zpwr-daw — JUCE / C++ DAW arranger (WebView host)
• zpwr-embed-terminal — the sibling shared embedded-terminal component