SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
View Poll Results: When will you switch to Wayland in Slackware?
People, where did I ever write that it would be more a apple or windows clone?
I wrote about user experience.
If you look at both apple and microsoft desktop machines, user experience is about smoother graphics, faster reactions. easier extendable.
User experience (UX) involves a person's emotions about using a particular product, system or service. User experience highlights the experiential, affective, meaningful and valuable aspects of human-computer interaction and product ownership. Additionally, it includes a person’s perceptions of the practical aspects such as utility, ease of use and efficiency of the system. User experience is subjective in nature because it is about individual perception and thought with respect to the system. User experience is dynamic as it is constantly modified over time due to changing circumstances and new innovations.
ISO 9241-210[1] defines user experience as "a person's perceptions and responses that result from the use or anticipated use of a product, system or service". According to the ISO definition user experience includes all the users' emotions, beliefs, preferences, perceptions, physical and psychological responses, behaviors and accomplishments that occur before, during and after use. The ISO also list three factors that influence user experience: system, user and the context of use.
Some of us view the windows and mac "user experience" as akin to swimming in a pool of liquid dog feces.
I am willing to try it. If it can work better for managing access to the display for things like virtual machines also running X or Wayland, then I'm all for it. My goal is being able to do "one chord" screen/display switching among MANY (60+) workspaces/desktops and full display processes like VM engines.
I would like to know how it would support older games like the original Unreal Tournament (made in 1999), which I still write mods for. I'm guessing that since it uses OpenGL there wouldn't be a problem, but it'd be nice to find out one way or the other.
I vote to switch when Pat/Slackware switches. Also, as some of you may know, I'm a devout fluxboxer so I guess when fluxbox supports it too that'd be optimal for me.
For all I'm concerned, things are still too fragile even after decades of development.. I recently upgraded packages on a machine using the "official" upgrade method, hosed half of it by doing so. Another machine just upgraded after perhaps a year not updating, the nvidia driver started shitting all over the place, I had to install the new version and now I'm stuck with horrible video issues (choppy playback, visual tear, etc). Instead of moving forward, for the time being, I will restore the clone I made about 8 months ago, when things were snappy and working well..
With other distros, if their package manager is smart enough to manage package versions and inter-dependencies, then its just a matter of upgrading/downgrading, and only bandwidth usage, on slackware since everything is very basic and manual, no need for me to toast one of my machines once more...
No im not planning upgrading or moving to wayland...
When Pat decides to move slackware toward wayland, it'll have to be so transparent to me that I wouldnt know.. Well, it'll have to be AS GOOD as X is now.. Otherwise, Im out.
Some of us view the windows and mac "user experience" as akin to swimming in a pool of liquid dog feces.
I wouldn't say that ill of Windows due to the fact I understand it fundamentally. I akin it to swimming in a pool of overly-chlorinated water that tends to burn the eyes a bit and leave you feels a bit dried out afterwards, whereas OSX is like diving into a sewage retention pond filled with whatever the city dumped in it. BSD and Linux is like a natural river and stream in the mountains, though I do suspect something upstream in Linux's river is causing the fish to start to die off.
Wayland should be transparent in transition, as it's supported to support all of the classic X.Org features.
If any of you has 45 minutes to spare, here is a very nice talk about Wayland by one of its developers (also an X developer). He very nicely explains why Wayland was a necessity. He also explains how the X network transparency is a myth nowadays (*gasp*) and how it might work better with wayland.
I think the DBus design decisions are good and correct.
I don't have any issues with X11 network transparency. It depends on applications. The crappy ones I don't need and I don't use, that includes KDE.
BTW: RDP mimics X11 the for GDI and is seen as mandatory in the industry. Transferring bitmaps over the network (like VNC does) is a thing from the stone age.
I don't have any issues with X11 network transparency. It depends on applications. The crappy ones I don't need and I don't use, that includes KDE.
BTW: RDP mimics X11 the for GDI and is seen as mandatory in the industry. Transferring bitmaps over the network (like VNC does) is a thing from the stone age.
If you don't only use Motif applications the Xserver acts quite similar to VNC, actually, since no modern toolkit lets the Xserver render their content. You actually have no network transparency, but are already transferring bitmaps. Also explained in the video linked by serafean. Nice watch, by the way, thanks for the link.
I managed to build wayland + weston and run it over KMS, with no X present. Also XWayland (X compatibility layer). Saw a few crashes, but the compositing quality is superb. Screenshot here:
Qweasd, did you find any specific noticeable differences in how XWayland operates compared to the standard X.Org server such as commands, setup, desktop environment support, etc. other than the Compositing?
Can't tell you much, only played with it for a few hours. The setup is zero-like: it just goes into Weston, which listens for X clients, if any. Weston itself is quite Spartan, but very smooth. I am sure I could run whatever in a full-screened xnest, I'll be checking on that. I also want to run some time benchmarks to compare xwayland with plain x.org, but time is something I ain't got a lot of
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.