jakeandameer2468
e51a58fe28
* fix(UI): remove the swift code that was causing the top bar to show when the window is maximized * fix(UI): limit the keybind handler to the `$libraryId` layout The keybind handler is how we get MacOS menu bar events to the front-end, and to navigate to the settings page correctly we need the current library UUID. We should hide/disable the settings button (and any future buttons that require a library/certain state - e.g. during onboarding) from the menu bar. * chore(swift): remove unused function * fix(UI): git didn't detect hook rename * fix(deps): revert tauri version downgrade Was probably caused by a bad merge * fix(UI): remove rounding of window borders on macos This was allowing the borders to still show on MacOS, despite the app being fully maximized. This doesn't impact non-maximized styling of the app, as we have native window decorations enabled within the Tauri config (well, that's my best guess as to why this fixes the issue). * fix(UI): conditionally enable/disable menu items on macos This is dependent on whether a library is present or not. If there's no library, we disable things such as copy/paste/select all. * fix(UI): try and conditionally show the border radius I think some cached files aren't being rebuilt correctly as this *should* work fine, it uses the same conditions as the traffic lights do to determine if we're fullscreen or not. * remove copy/select all/paste as they have uses outside of the explorer * feat(UI): overhaul native macos menu * fix: add toast for quick rescan and free up the ctrl+r keybind * more menu rearrangements * update menu further * add comment about rounded edges * some polish * add working overview redirect * fix(UI): correct border edges when non-maximized, and full corners when maximized * cleanup event handling * add media view and disable non-working buttons * fix(UI): raise sidebar on fullscreen to prevent empty corner * adjust settings padding when maximized on macos * failed sidebar animation * rm old stuff * fix(UI): better transitions (i'm learning!) * add comment about why new library is disabled during onboarding * make the settings page static and `pt-6` * add mock-up library selector in menu * `maximized` -> `fullScreen` * fix animation when fullscreening * clippy * change animation to 300ms --------- Co-authored-by: ameer2468 <33054370+ameer2468@users.noreply.github.com>
Spacedrive
A file explorer from the future.
spacedrive.com »
Download for
macOS (Apple Silicon |
Intel) ·
Windows ·
Linux ·
iOS ·
Android
~ Links for iOS & Android will be added once a release is available. ~
Spacedrive is an open source cross-platform file manager, powered by a virtual distributed filesystem (VDFS) written in Rust.
UPDATE: Spacedrive is under active development, we are in the alpha stage and some features might be missing or disabled in the official release downloads.
Organize files across many devices in one place. From cloud services to offline hard drives, Spacedrive combines the storage capacity and processing power of your devices into one personal distributed cloud, that is both secure and intuitive to use.
For independent creatives, hoarders and those that want to own their digital footprint, Spacedrive provides a free file management experience like no other.
What is a VDFS?
A VDFS (virtual distributed filesystem) is a filesystem designed to work across a variety of storage layers. With a uniform API to manipulate and access content across many devices, VDFS is not restricted to a single machine. It achieves this by maintaining a virtual index of all storage locations, synchronizing the database between clients in realtime. This implementation also uses CAS (Content-addressable storage) to uniquely identify files, while keeping record of logical file paths relative to the storage locations.
The first implementation of a VDFS can be found in this UC Berkeley paper by Haoyuan Li. This paper describes its use for cloud computing, however the underlying concepts can be translated to open consumer software.
Motivation
Many of us have multiple cloud accounts, drives that aren’t backed up and data at risk of loss. We depend on cloud services like Google Photos and iCloud, but are locked in with limited capacity and almost zero interoperability between services and operating systems. Photo albums shouldn’t be stuck in a device ecosystem, or harvested for advertising data. They should be OS agnostic, permanent and personally owned. Data we create is our legacy, that will long outlive us—open source technology is the only way to ensure we retain absolute control over the data that defines our lives, at unlimited scale.
Roadmap
View a list of our planned features here: spacedrive.com/roadmap
Developer Guide
Please refer to the contributing guide for how to install Spacedrive from sources.
Security Policy
Please refer to the security policy for details and information on how to responsibly report a security vulnerability or issue.
Architecture
This project is using what I'm calling the "PRRTT" stack (Prisma, Rust, React, TypeScript, Tauri).
- Prisma on the front-end? 🤯 Made possible thanks to prisma-client-rust, developed by Brendonovich. Gives us access to the powerful migration CLI in development, along with the Prisma syntax for our schema. The application bundles with the Prisma query engine and codegen for a beautiful Rust API. Our lightweight migration runner is custom built for a desktop app context.
- Tauri allows us to create a pure Rust native OS webview, without the overhead of your average Electron app. This brings the bundle size and average memory usage down dramatically. It also contributes to a more native feel, especially on macOS due to Safari's close integration with the OS.
- We also use rspc which allows us to define functions in Rust and call them on the Typescript frontend in a completely typesafe manner, so no unnecessary bugs make it into production!
- The core (
sdcore) is written in pure Rust.
Monorepo structure:
Apps:
desktop: A Tauri app.mobile: A React Native app.web: A React webapp.landing: A React app using Vite SSR & Vite pages.
Core:
core: The Rust core, referred to internally assdcore. Contains filesystem, database and networking logic. Can be deployed in a variety of host applications.
Packages:
client: A TypeScript client library to handle dataflow via RPC between UI and the Rust core.ui: A React Shared component library.interface: The complete user interface in React (used by appsdesktop,webandlanding)config:eslintconfigurations (includeseslint-config-next,eslint-config-prettierand alltsconfig.jsonconfigs used throughout the monorepo.macos: A Swift Native binary for MacOS system extensions.ios: A Swift Native binary (planned).windows: A C# Native binary (planned).android: A Kotlin Native binary (planned).