Now that @X512 has reach a breakthrough with the GPU, makes room for sugar and blur and all that appealing ui look . I know some body is going to say, when you put in the work, Iām Just excited.
Note that that whole discussion was before you could swap controllooks easily. Nowadays there already is not that much in the way of making a ācandyā UI.
the only thing missing/troubling would be the lack of a window compositor, which makes shadows easier, and ācoolā efffects like window transitions⦠however it is not required for all of them. (i.e a āminimizeā animation can just use the last frame as a screenshot of a window, it does not need to have this as an off-screen canvas)
IMO there are three main benefits of having a compositor:
Non-regular shaped windows (see Dockbert and HiQDock, for example)
Semi-transparent windows for things like OSD (volume, brightness, etc.)
Screencasting: for example, recording the content of a hidden or off-screen window,
Personally, I donāt care much about fancy transitions like in MacOS but the three above would make a huge difference.
To be honest, Iām not sure if we actually need a compositor for no. 1. maybe a mask is sufficient and perhaps, this is how it was implemented in BeOS R5.1 aka Dano.
nr 1 does not require a compositor, and nr 3 can argueably be implemented with off-screen surfaces directly⦠that does not neccesarily require compositong the other parts off the desktop hower.
I do not see any problems with the current GUI. Maybe if its all (the features discussed in this post) implemented and not a default config and the current default stays as the main one, i would be fine. I think there is a large number of people here that think haiku UI is the best today and some who even revert to the BeOS decorations and change to a more Classic mac-like theme (i do both). I am also sure most here are not fond of GUIs like KDE, Gnome and current Windows and Mac UIs.
And i also think it makes sense that the default GUI will be the one that is utilized in non-gpu acceleration contexts (the overwhelming majority of all likely current and future haiku installs), as it is very hard to support all x86-64 machines and x86 machines from the 90s to now in terms of gpu driver support, not considering also the fact they would be slow in acceleration.
I donāt think Haiku, is only about looking a certain way, there are other benefits to Haiku like, a unified app packaging format, speed, and just the fact that the world could use one more powerful kernel. But assuming that all users like haiku because they want to revive old 90ās computers and therefore undermining the need for GPU acceleration is, hmmm.
More seriously though, I would rather not have Haiku be too glossy and stray too far from its now-distinctive aesthetic.
A couple animations and transitions here and there might be fine, but no burning close windows please. An advantage of a more minimal approach to a composited desktop is having more VRAM for apps and games to use, which is helpful for both lower-end hardware that may struggle otherwise and top-end hardware which are often used for extremely GPU-intensive workloads (i.e. 3D work, gamedev, machine learning, etc.).
Still though, if thereās ever going to be any fun/marginally useful optional effects please let it be wobbly windows.
Iād like to see circular windows with movable tabs that can spin around the outside.
Other than that, I wouldnāt mind seeing some graphical improvements, as long as the core stuff isnāt done away with. Things like movable tabs, etc.
I specifically was talking about machines far wider in range than 90s machines but also including. Not to mention anyone trying haiku in a newer machine with unsupported GPUs would not have the ability to use these features. So defaulting to what it is now would be wise. In no moment i said anything should be undermined but that throwing software rendering out of the bus or leaving people with unoptimized animations and layers which will be slow in their more restricted machines (not anyone can afford a high-end nvidia gpu) would be unwise. It is something linux loves to do (also to break old drivers and functional hardware or dropping old drivers from repositories without any respect for users) which i think does not make sense in haiku and many likely agree
On Linux/wayland you can unredirect fullscreen windows and allow tearing. But for regular desktop usage the features a compositor bring are worth a couple frames of latency.
Same here,feel free to implement fancy but useless effects,but donāt force them on me.
I know that some people like them,but forcing them is the route Windows,MacOS and most Linux desktops have already gone and I hate them for being so painfully slow.
I prefer a clean and responsive desktop with 90s-era design and no bloat.
This might be possible with displays that support adaptive sync, but clasically compositors would use vsync which gives one frame in effect (and for some reason some compositors have even moreā¦)