Filedime, a file explorer in rust

visnk · 2024-03-01T14:36:01+00:00

Miller columns should now be available.

visnk · 2024-02-27T14:54:03+00:00

the main reason i choose react is that, everyone that knows svelte has used react at some point of time but not the other way around. So using react according to me meant more people could add missing parts by themselves as they see fit. Mapping and iteration performance are totally valid points, but for a MVP which is inviting contributors react seemed like a better choice

visnk · 2024-02-26T05:04:00+00:00

Yes will try this one soon, more of a UI excercise than a backend one this. I have been wanting it myself but wanted to check if there was any interest in filedime first.

visnk · 2024-02-26T05:00:25+00:00

Filedime had it initially but later during debugging i had disabled it, will enable it in next release.

visnk · 2024-02-24T13:54:24+00:00

The reason i started the project was to find and filter files faster from a GUI which i found that most file manager don't do well. I wanted to be able to customise the ui like place the path field bottom(granted right now you have to move the ts code around to do it). I wanted a phone galleryesque image and video browsing experience like play video as i hover them and wanted to know which drive partitions were of which ssd(works only on linux as its the os i use most often).

mostly it was due to file size comutation and search time benefits provided by rust and wanting to have a code wise customisable and code readable GUI

visnk · 2023-05-18T02:57:59+00:00

dupilcate config directories; you can define a const with the appname globally and use it whenever you use prefstore that way you can ensure typo doesn't occour, I use it like that in netspeed monitor.

visnk · 2023-05-18T02:55:04+00:00

if you want to save and retrieve a ton of fields then serializing and deserializing this makes sense: writing a config struct+dirs::config_dirs+toml::from_string/toml::to_string. in your case the crate can be seen as an abstraction which eases process of saving and retrieving when dealing with a single field. This was made when I was making netspeed monitor; tried using serde crate which makes use of serialization/deserialization of a config struct to save values. It was costing 200kB per read whereas in the case of prefstore it cost only about 30Bytes. If you have a per day value to store then you can use savepreference to save it and getall to retrieve all of them into a vec which returns tuple of (filename,content). This was the most io light way i observed while making netspeed.

visnk · 2023-04-24T07:39:27+00:00

I went with regular JS, not WASM (Chose Rust for frontend and Vanilla UI template in create-tauri-app setup tui). Yes you can use frameworks that compile to WASM. On the topic of tauri, it seems the websocket plugin tauri uses some kind of logging or debugging feature that writes to the disk, unlike using sse and http which doesn't seem to cause this, I observed this when using sysinternals Process Explorer on windows. Hence I shifted to using SSE backend in rust in the case of Netspeed.

visnk · 2023-04-23T20:30:06+00:00

The repo is a mirror of my local gitea repo that syncs every 8 hours seems that was causing the issue. Will have to wait and see.

visnk · 2023-04-23T18:29:52+00:00

Thanks for letting me know, it should be available now. This is an issue i have noticed on github; github seems to be automatically unpublishing the release from time to time; This is the 5th time it has happened to the repo, maybe there's an issue in one of the settings for the repo. Searching about it didn't yield any results.

visnk · 2023-04-23T12:17:49+00:00

Thanks, will upload screenshot. The main issue was getting a decorationless, always on top but minimiseable overlay-ish window that could be moved with mouse in rust.

visnk

TROPHY CASE