How onefolderapp/onefolder works
Project type and purpose
• This is an Electron-based desktop application (“OneFolder”) for browsing and editing photo metadata in place (no separate DB), using React/MobX for the UI, Node/Electron for filesystem & native calls, WebAssembly for performance-sensitive tasks, and ExifTool for metadata I/O.
File structure
• Top-level:
• src/main.ts – Electron main (Node) process entry
• src/renderer.tsx + src/frontend – React renderer process
• src/ipc – message definitions + bridging code between main & renderer
• src/backend – background schedulers & file watchers in main process
• src/api – shared TypeScript abstractions for file/metadata operations
• wasm/… – Rust-based modules compiled to WebAssembly for image decoding & layout
• src/frontend/workers – Web Workers wrapping WASM and heavy tasks (thumbnail gen, hashing, folder watcher)
• resources/exiftool – bundled ExifTool CLI for native metadata operations
• Config & build: webpack.dev.js / webpack.prod.js, electron-builder in package.json
• Tests span backend, utils, and front-end components.
README for additional insights
• Architecture hints: Electron + React + MobX, ExifTool for metadata, Annotorious + TensorFlow.js for face annotation, WebAssembly for performance.
Detail but avoid over-splitting
• Essential layers: UI components, Stores, IPC, Main process services, Workers, WASM, ExifTool, File System
• Do not drown the viewer in every React component—group by “UI Layer” or “ContentView, Outliner, Settings”
• Call out specialized modules (e.g. FaceDetection, ThumbnailGen) individually