Originally posted by dreich
View Post
Announcement
Collapse
No announcement yet.
Hikari 2.2 Wayland Compositor Adds Support For WayVNC, Other Features
Collapse
X
-
-
Originally posted by birdie View PostSo, another WayLand compositor without a taskbar? Who uses this crap other than their own developers?Originally posted by kpedersen View Post...now we basically rely on a single guys hobby project? Something doesn't seem quite right.Originally posted by acobar View PostMy main critic toward Wayland was always about how to just specify a protocol is a stupid decision that would generate fragmentation and incompatibilities on the long run...
Maybe if Hikari came with cute mascot and anime wallpaper maybe I would use, I would definitely use it.
- Likes 1
Comment
-
Originally posted by birdie View Post
Are you saying it's taken them 12 years to implement a taskbar (API)? No wonder most people and serious companies do not give a damn about Wayland. Such a wonderful lightweight ... unusable graphics protocol.
That far-too-long sentence aside, it still seems to be a great graphics protocol, but incomplete without extensions (as it was intended to be in order to fit other incompatible use-cases) and we've finally got something of a wayland community rather than a set of silos led by the biggest powers in desktop Linux. I'm pretty sure libweston is only used in commercial products because I can't find any compositor beyond weston itself that actually still uses it -- they all moved to wlroots. I wish it was 12 years ago too, but it seems like now we really start the countdown for when wayland by default seems more like a comfortable upgrade rather than tinkering, masochism, or limited needs.
- Likes 3
Comment
-
Originally posted by BwackNinja View Post
There's already a protocol for that, wlr-foreign-toplevel-management. Hikari doesn't support that (at least yet), but any wayland compositor that supports both that and layer-shell can use a panel like mate-panel. This includes wayfire and sway (which are both built on wlroots), and mir ( https://github.com/MirServer/mir/pull/1684 ).
Comment
-
Originally posted by birdie View PostSo, another WayLand compositor without a taskbar? Who uses this crap other than their own developers? Why is it so difficult to have this feature implemented in Wayland when it's available in absolute most X.org DEs/Window Managers/whatever?
I would much rather have some kind of mechanism to tile all the open windows into clickable thumbnails like what Gnome and Plasma offer when there is a need to switch between various windows to get things done. This is the one missing feature from Weston that prevents me from using it as a daily desktop interface. Which is a real pity because Weston actually works (mostly) with Firefox on Wayland and Ozone Chromium with the Wayland option, both of which still do not run on Debian 10's bundled version of Plasma Wayland.
- Likes 1
Comment
-
Originally posted by set135
I think this illustrates a fundamental misunderstanding about Wayland that many people around here have. Wayland was purposefully designed to be a minimal graphics rendering protocol that can be extended as use cases occur that implementations desire. A taskbar (something I have no use for) is part of a certain desktop paradigm, and so it falls to those implementing compositors to implement it, and if the Wayland protocol requires an extension to facilitate that, then it can be added. Similarly, remote display over a network was not designed in, because it can be added later as implementers require. People get exercised because they think that their personal (often faddish) conception of a desktop is the only obvious and true thing that that should have been explicitly designed for to start with. There are other use cases, such as IVI, kiosks, fanciful things like mapping your windows onto rotating klein bottles (Where are your cartesian coordinates now?), tiling vs layered windows, etc. Not trying to make design assumptions from the beginning was because of the lessons learned from X11-- probably very few people here will eg. know what applications using the Athena widgets look like and would be *horrified*, but that uses cutting edge assumptions designed into X11, like rendering primitives to draw circles and rectangles, etc.
Also, it helps to realize that X11 took decades to add the features people require to run a modern desktop, and that the window managers and compositors people have become used to would be impossible for most of X11s life. Wayland and the compositors using it will continue to develop and add desired functionality over time, and as usual the utilities and libraries will become more comprehensive. Now that major desktops and vendors are starting to offer things that more end users encounter, this process will accelerate.
- Likes 1
Comment
-
Originally posted by hax0r View Post
Couldn't agree more. Somebody bring Linux Hater blog back to life, not much changed regarding usability/responsivity/fluidity/latency/unity/elegance of GNU/Linux on desktops in last 10 years. Linux sucks on desktops as much as ever. Wayland is dead.
Maybe if Hikari came with cute mascot and anime wallpaper maybe I would use, I would definitely use it.
Comment
-
Originally posted by birdie View PostSo, another WayLand compositor without a taskbar? Who uses this crap other than their own developers? Why is it so difficult to have this feature implemented in Wayland when it's available in absolute most X.org DEs/Window Managers/whatever?
I don't use a taskbar as they aren't really useful when you're using a tiling window manager. But they do exist.
Comment
-
Originally posted by kpedersen View PostBack in the day we had at least 10 large corporations developing and testing things like libX11 and yet now we basically rely on a single guys hobby project? Something doesn't seem quite right.
Comment
Comment