@SysError06

Frostclip, my beautiful game clipper (Medal.tv, ShadowPlayer) alternative, now in rust!

Boy this was something else. I thought to myself, “Go doesn’t fit my needs anymore, so Rust is the natural option”. And boy how Rust humbled me, errors upon errors. To simple logging issues to unused variables to borrow checking and memory issues, to muxxing, encoding, capturing. The whole lot!

Currently, I don’t even have a quarter of the app working, it only works on Intel/AMD gpus on Linux, with macOS, Windows, and NVIDIA support yet to even be started.

here, have a screenshot of my abomination

Custom desktop and accent colors!

I added a modular color picker component in the Personalization settings panel. Clicking a preset or using the native eye-dropper custom color tool instantly updates buttons, icons, switches, and highlights across the entire OS. I also implemented a FileReader data-stream pipeline. Users can upload any .jpg, .png, or .webp file from their local machine, converting it to a base64 string to update the active desktop background immediately. Also, if a user doesn’t have a custom wallpaper, the default desktop gradient now intelligently samples the chosen accent color, blending a low-opacity hue directly into the dark/light background.

Alt tabbing (sort of).

A lot of this time was spent refactoring the window system to use a windows object.

To start off, I tried adding a navigator.connection API to try and identify cellular vs wifi vs ethernet structures, however as of reading the MDN docs it turns out its not a very common API, with Firefox dropping it as of Firefox 31, and Safari never having it in the first place, I ended up switching to the onLine/offLine property, which is supported by all mainstream browsers.

Also Alt + tab is currently slightly broken, as it does not yet show a window preview, as well as not properly focusing the chosen window, however this is something I will tackle later on, as I plan on adding custom wallpaper support now.

(flashbang warning)

Light mode!

Changes CSS values to respect the theme detection, also tries auto detect light/dark mode based on browser settings.

Oh yes also changed up the topbar to look better (looks alot more like macOS now which I may change in the future.)

Simple stuff this time around, just made the desktop look more like macOS, will probably edit though so it doesn’t look TOO similar. Will add the ability to change dark/light mode and background next!

So, A LOT of time was spent on this, a lot more than I anticipated. Firstly, I added a new settings app (which currently only has like one setting) that uses shadcn’s components for switches, buttons, sliders, etc. This was because I did NOT want to make my own components from scratch. Quick look at the docs, I added my necessary components, and CSS theming. I had a slight issue with setting raw CSS variables on .dark blocks weren’t syncing up properly with unedited shadcn svelte components due to Tailwind’s V4 theme compiler rules. Configuring custom colors directly in the @theme inline block in layout.css seemed to fix this. I also migrated the dock into its own components (Dock.svelte), allowing for better scalability.

Overall, pretty happy with this session, as now I can seamlessly add settings, add components, app, and all. The new task is to clean up the desktop, making it more visually appealing to the eyes.

Not much was doen apart from porting the gh pages to SvelteKit

Was done by making a deploy.yml workflow that builds the website and deploys it to GitHub Pages. Next plan of action is cleaning up desktop to make it more pleasing on the eyes

Sigh….. I got bored

I hate vanilla html and javascript, so…. I switched my webOS entirely to SvelteKit.

This change should help me add components easier, also can add better stuff, I have also switched from base CSS to TailwindCSS, which is what I’m more used to. What I plan on doing is making every app its own svelte page, making it really easy to add apps. Overall nothing changed for now, I just spent the time porting over to SvelteKit.

First devlog of berryOS!

This is part of the webOS mission, however I am already pretty experienced in web devving so I kinda improvised on some stuff. I got an app dock, windows, topbar, time and a background!

Devlog #7

So here I am, making it…. again. I have also TRIED fixing some stuff, namely the bug where the sidebar moves with the amount of content displayed in the content panel (aka it moves up when the panel has less content). I tried many things, removing flexes, adding flexes, adding borders, adding frames, and removing vscroll_indicators. Nothing worked :(

I’m hopeless at this point. I’ve tried asking AI and all, yet nothing will go back at it later, I guess.

So I tried tackling another issue, making the directory display before the files. I had more luck with this one. All I did was make a std::sort step that parses all the contents from beginning to end and checks if it’s a directory; if it is, it will just display it on the content panel first!

Soon to come is adding some way to customise settings (or make a part of it to work on later), probably will just use enums like standard C++.

Devlog #6

My disk is very full!

Today, I thought to myself, “why haven’t I added a root disk stat yet, that shows usage and all that good stuff”

Well, here I am answering my thoughts. I’m not crazy… maybe. Basically for the backend I made a DiskStats struct that holds important variables , like used percentage, available bytes, used bytes etc. I then hooked that up to my filesystem cpp implementation, and tested it. Worked on the first try! Nice job C++! However, I noticed that not everyone would like to read thousands of numbers and convert them into megabytes, gigabytes etc. So I made a simple formatter util that does the job for you.

Next was the ui. I made a disk click handler (that currently doesn’t work) that show the disk stats, and has a progress bar that turns red if disk usage is over 90% (signalling critical usage limit). Then, I just piped that into my main view vbox.

Devlog #5

Icons, icons, icons!

Today, I decided to finally add file icons to the content page finally. Overall, it wasn’t particularly hard, just VERY tedious to do. I used nerdfonts to render the icon. It took me the majority of my time actually setting all the icons, with their numerous file extensions. .so, .py, .elf, makefile, docker, csharp, cpp, h, hpp, c, you name it.

But hey it looks prettier now.

Devlog #4

Decentralisation

Today (and yesterday to a certain extent), I have worked on decentralising the ui components into their own respective files.

Of course, this didn’t come without its numerous issues, namely being the C++ pointer errors striking yet again. Overall, the transistion wasn’t too hard, so I got to making a breadcrumb for the filepath. However, during the making of this, I noticed that the sidebar options weren’t properly sending me to the path, I fixed this by injecting the / path into the second slot of the target array inside my SidebarComponent.

Devlog #3

Welcome to the horrors of C++

I’ve officially split the file manager into a dual-panel desktop layout featuring a fixed “Places” sidebar and an overflowing “Content” directory using FTXUI’s DOM elements (elements.hpp). The trickiest part was getting large directories to scroll smoothly instead of truncating off-screen, which I solved using frame and vscroll_indicator viewports.

Of course, C++ warmly welcomed me to modular architecture by throwing a brutal std::length_error core dump after spending a solid 15 minutes refactoring my main.cpp into multiple modular files. I spent a considerable amount of time fighting what I thought was bad memory management, only to realise I had used an unsafe raw pointer cast on a boolean flag inside my tab container, forcing the layout engine to read random garbage bytes. At least that’s what I thought it was; in reality, it was that my change_directory function calls update_directory, which does display_names.clear() and rebuilds the vector. However, ftxui’s Menu component holds a raw pointer to the origin vector, but the vectors’ internal buffer got reallocated when it grows beyond capacity. With the issue identified and fixed, it now works again! Sort of…… now the directory contents don’t sync properly due to my fixes, including proper resyncing to avoid a SIGARBT.

With the code cleanly refactored into separate files and building, I’m aiming to tackle a dynamic file path bar and a basic context menu next.

Devlog #2

Implemented a basic escape menu system, currently hoping to be similar to btop++, effectively just btop but a file manager.

Hello everybody!

To start of, I am a power user. I hate the concept of using a mouse to navigate around my system, its just so… slow and tedious. To fix this, I have aggressively tried to make my system as keyboard centric as possible. Whether that be switching to Linux, using a tiled window manager, or anything like that. My only problem, my file manager, I would like a file manager keyboard friendly, yes there are options but I wish to make my own, so here I am.

For now, I’ve setup basic filesystem indexxing, alongside a tui implementation (without much features as of now). Progress is being made, however I’m far from complete.