this post was submitted on 03 Jul 2026
61 points (96.9% liked)

Opensource

6387 readers
166 users here now

A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!

CreditsIcon base by Lorc under CC BY 3.0 with modifications to add a gradient

⠀

founded 2 years ago
MODERATORS
pylapp@programming.dev
61
GUI for my OS (D.eSystem 6.0.6 alpha) (lemmy.world)
submitted 1 week ago by D_elec_dev@lemmy.world to c/opensource@programming.dev
13 comments fedilink hide all child comments
 

Hello everyone!!

D.eSystem 6.0.6 alpha introduces the first GUI for my operating system D.eSystem 6.

The system is currently keyboard‑only, but mouse support is planned for future versions.

The usage is similar to D.eSystem 6.0.5, but now with a graphical interface, and the calculator also received a GUI version.

Requirements:

64‑bit CPU

UEFI firmware (Legacy BIOS is not supported)

D.eSystem 6.0.6 alpha runs on any VM (QEMU, VirtualBox, VMware) and on real hardware.

Download D.eSystem 6.0.6 alpha here: https://github.com/D-electronics-scratch/D.eSystem-6.0.6-alpha-iso-download

top 13 comments
sorted by: hot top controversial new old
[–] GreenKnight23@lemmy.world 17 points 1 week ago (1 children)

don't pull a Temple, take time off and prioritize your personal health and wellness.

[–] D_elec_dev@lemmy.world 10 points 1 week ago

Yes,I have a routine when I am coding,mostly I am coding at evening or wecken, I also do other stuff,thanks for your tip

[–] outabisnes@reddthat.com 12 points 1 week ago (1 children)

Looks very interesting, will definitely try to play around with this if I find a free minute at some point.

One thing that struck my eye is your use of github repositories which I am not fully understanding. Is there a specific reason for having each major and minor version of the OS as a separate git repository with only a single real commit, and each iso download as another separate git repository?

In my mind it seems so antithetical to tracing the development history that right now I am scratching my head at it a little.

[–] D_elec_dev@lemmy.world 5 points 1 week ago (3 children)

Should I only have one reposotory?

[–] rimu@piefed.social 9 points 1 week ago

That is the convention. It is also common for devs to make a new branch for each release so you can issue updates for that version by adding a commit to that branch.

[–] one_old_coder@piefed.social 4 points 1 week ago (1 children)

Definitely one and only one repository where the "versions / releases" are branches or tags. That way, you can compare your versions with git, fix an old version, etc.

Having multiple repositories is a PITA for you and for others.

I like this branching strategy but you can use your own: https://trunkbaseddevelopment.com/

[–] D_elec_dev@lemmy.world 1 points 1 week ago

Ok,thanks for your tip

[–] Lumisal@lemmy.world 2 points 1 week ago (1 children)

You should also have a backup somewhere else every other major release in case GitHub glitches out and decides to delete your account, or marks it as malware or such. It's happened to even better known projects like KitchenOwl.

[–] D_elec_dev@lemmy.world 0 points 1 week ago

Yes,I have a backup local on a USB drive,I save there every version from D.eSystem 6

[–] asudox@lemmy.asudox.dev 5 points 1 week ago* (last edited 1 week ago) (1 children)

Cool, but where is the source code?

edit: found it https://github.com/D-electronics-scratch/D.eSystem_alpha-6.0.6

[–] kata1yst@sh.itjust.works 5 points 1 week ago

Hmmm not sure that's the complete source code. Most of those files are very high level, 8 - 80 lines of code. I'd expect there's something not in the repo doing a ton of the heavy lifting.

[–] Marija@programming.dev 2 points 1 week ago (1 children)

Nice, looking cleaner already