Carl Svensson on why desktop user interfaces haven't evolved much:

"To me, trying to reinvent the desktop experience feels a bit like complaining about steering wheels in cars."

https://www.datagubbe.se/futui

#FreeBSD will not ever break into the real desktop market at any time because their core developers did not learn to hack monitors or offer better #GUI options. I think they're still stuck in 1999?

I'm using the latest version of FreeBSD. I tried installing xorg/xfce/slim...

And even when I put efi_max_resolution="1080p" and those two oddball exec settings referencing gop set 0; gop set 2 into /boot/loader.conf FreeBSD still DOESN'T WORK on a modern HDMI monitor using an older PC.

How is this my fault, again -- guys? Get a brain.

Instead I'm stuck with the very low resolution of 640x480. I hate that resolution. It's so... 1990.

Whichever high priest in the European or American BSD camp that is keeping their code this way is a total asshole. No one can work with that.

Sure, I could use DragonflyBSD or something else. But I don't want to waste my time experimenting with their exclusive version (and likely those people are making use of a different package manger than the one I'm used to, already).

So yeah, FreeBSD is more or less *permanently* a headless or server OS thanks to their treatment of users in this way.

A new version (0.7.3.0) of nodgui, a simple GUI library for Common Lisp, has been released: this is a feature release.

From the NEWS file:
- [new feature]
- added virtual keyboard widget;
- added label spinbox widget;
- [pixel-buffer] added multitexture polygon rendering;
- added function to manipulate tags in canvas items (add/remove tags and find items by tags)
- added `grid-implicit', a function that fill the next available row with widgets in a single call, without specify columns.
- [improvements]
-Enable use of `asdf:test-system`, thanks fosskers!
- [bugfix]
- fixed regression: restored support for TGA bitmap file format
- removed 'eval-when' around ~+2pi+~ definition to prevent error when compiling code, without loading the source (thanks to the person that reported this issue!).

Nodgui is copylefted free software released under LLGPL license.

- web page
https://www.autistici.org/interzona/nodgui.html

- source repository
https://codeberg.org/cage/nodgui/

Bye!
C.

I need to keep up with my favourite #linux #blog @omgubuntu

I saw that Gnome has a new website, it looks great, and their software looks beautiful.

We are so spoiled in the Linux community to have such amazing projects - the kernel, software, OSes #GUI... all of it!

What I don't get is the amount and level of people's rage at something they are getting for free. I can't contribute to fix, so I just move to something else that works for me and try again later.

https://www.gnome.org/

#TIL: there is some fuzz around #SwiftLang usage on non-#Apple platforms. There was a whole devroom at #FOSDEM yesterday showing use cases such as #embedded, #backend as well as #gui development - incl. a #swiftui like cross-platform library: https://adwaita-swift.aparoksha.dev/tutorials/table-of-contents/

Spent the last 6 hours trying to get a hello world equivalent gui window with a button on rust under windows.

This task which one might think is simple ended up taking literal hours and still hasn't been achieved because: the tutorials for gtk on windows and rust suggest putting msys2 bin directory on the path. This causes rust to fail to build correctly because it uses the wrong gcc and linkers.
Afterwards I managed it by using the appropriate environment variables.
But then I found out the dynamically linked libarries weren't found. I tried getting a way to copy them but it turned out to be too much work so I just moved the executable to the same dir.
Only to find out that gtk4 has no accessibility on Windows. Not bad accessibility, not accessibility that needs to be turned on. No. Accessibility. At all.
So then I decided to try Qt, which wants me to create an account to get an installer. Absolute no.
Got the 1.5gb sources and trying now to get an off-line installer out of it.

To get a fucking window with a button in it.

I don't think it's unreasonable for me to say this state of affairs is complete bullshit, and that most people with a normal level of motivation would have found plenty of opportunities to have given up. I still might.

(Not using NWG because tying the data to the GUI elements is non-trivial, it seems to require copying a lot and using twice the memory.)

Meet YQPkg: package management on #openSUSE! A lightweight, standalone #GUI alternative to #YaST, now in alpha. Try it out and help shape its evolution! https://news.opensuse.org/2024/12/20/new-pkg-mgmt-tool-debuts/

Any sugestion on learning to make gui, as in code them, while not using JS or web tools?

Like a simple "this is how you push pixels to the framebuffer in a couple of lines of code" and "this is how you catch mouse/keyboard events" guide.

I want to learn how to do it low level. But it would be easier to get going with a good guide on where to even start.

Keeping data in sync while avoiding event listener loops in #Java #JavaSwing is a huge pain in the butt.

One mistake could create a bug where the right combination of user actions will make the GUI become inconsistent with the real state of the program, or worse, freeze and consume 100% CPU! Yikes.

I've heard that immediate-mode #GUI doesn't suffer from this problem. Certainly seems tempting. But it does rather infamously suffer from poor performance (e.g. #React), so…

Today, in my search for a way to create GUI applications without suffering, I have looked into Pascal, which seemed like a nice language with a mature environment for this purpose.

Playing around with the language, I ran into an odd error: Pascal allows one to set boundaries for an array, and each boundary may be specified using a constant one has declared earlier. However, this doesn’t work if a type is declared for said constant.

After some time spent searching, I found a forum thread where the issue is explained thusly:

e.g. using a typed constant allows you to actually change the value of the constant.

Object Pascal offers two different sorts of consts: ‘proper’ consts that are constant (as you might expect), and typed consts that are initialized variables. Naming the latter sort ‘const’ is a frequent source of confusion for newcomers to Pascal, but it was introduced by Borland, and FPC preserves the same syntax for compatibility with Delphi.

So in this language, which has separate declarations for constants and variables, there is a non-obvious way to disguise the latter as the former, for historical reasons. If that’s any indication of what one may expect from the rest of Pascal…

… there’s no way! There’s just no way to make a GUI application without suffering, is there?!

#Doom #GUI #HUD
Finally, первая стабильная версия моего HUD'а для Doom.
Github
Ну... Я надеюсь, что мне и в ZDoom пропустят пост (и разрешат BBCode хотябы на 1 пост)