Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Preparing for KDE Plasma's Last X11-Supported Release

blog.davidedmundson.co.uk

Post reply on HN
Print view View original

291–300 of 392 posts

Re: Preparing for KDE Plasma's Last X11-Supported Release

#291

Post by thesuitonym »

gmueckl wrote: post #170
thesuitonym wrote: post #150

Earlier quoted context omitted.

If things were designed well, it would be as easy as clicking the pin icon on the window border.

How many buttons do you want on a window frame then? The typical 4 buttons already take a lot of space in the title bar. Not everything that seems like a good idea at first glance is actually good design.

I don't know man, everybody is fine with putting tabs, and searchbars, and a bunch of other shit in the titlebar, but god forbid we put one button that's actually incredibly useful.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#292

Post by leephillips »

MBCook wrote: post #32
jebenesty wrote: post #25

Earlier quoted context omitted.

Did you really just [sic] a British guy using British spelling?

Is that a British spelling? Oops. Honestly my computer gave it a red underline so I decided to do that. I didn’t think about it harder than that. If I recognized it like “colour” I wouldn’t have.

And the “[sic]” is followed by an incorrect attempt to form a conditional. Both problems arise from the same cause.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#293

Post by dannyfritz07 »

The_President wrote: post #116
pseudalopex wrote: post #103

Plasma/Wayland Known Significant Issues[1] No ability to save and restore positions of native Wayland windows Real-fake-session-restored apps don't remember which virtual desktop their windows were on No full-screen aspect ratio correction "Spare Layouts" feature not implemented "Per-application Keyboard Layout" does not work No way to change the gamma or manually adjust the colors without generating or finding an ap…

The Bluetooth integration needs work - missing features such as "never connect automatically." Default lock screen experience still has a needless delay of 5 seconds when entering a wrong (even blank wrong) password, even on the first attempt. +1 on the gamma controls

Bluetooth autoconnect configuration is a Wayland issue? I honestly would have never guessed. I always figured it was the responsibility of the DE or bluez service.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#294

Post by NoboruWataya »

JNRowe wrote: post #254
NoboruWataya wrote: post #89

Slight tangent but has anyone moved from AwesomeWM to a Wayland-based tiling WM? Interested to hear what people chose. I tried Sway for a bit and while it's not bad by any means it's a bit too unlike what I'm used to. SomeWM is an attempt at "porting" AwesomeWM to Wayland and looks very promising but not quite there yet (I couldn't get Vicious widgets working and not sure if supporting them is even a goal). I'm still…

I settled on river¹ after a couple of decades with awesomewm. Tiling and tagging work in a way you'd expect coming from awesomewm, but nothing else does. I made my mind up because having to use workspaces and manual tiling is a far harder sell than implementing the functionality I want on top of a decent base. If anything it reminds me more of the experience with using awesome v2(before lua); you generate a config fi…

I had seen river but for some reason didn't look too much into it. I think it's because at first glance it looks like a protocol that you can build a WM on, rather than a WM itself, but I guess it's probably easy to build your own tooling over it (a lot easier than "building your own WM" in the traditional sense)?

I'll give it a look - thanks!

Re: Preparing for KDE Plasma's Last X11-Supported Release

#296

Post by kombine »

irthomasthomas wrote: post #287
KptMarchewa wrote: post #282

Earlier quoted context omitted.

[flagged]

Why do people only do this to the x11 guy? I bet if you interrogated the wayland side to the same degree you would find similar, or worse. Afterall, who is more likely to be the bad guy? The corporations hurting linux by killing accessibility and interoperability, or the guy giving his spare time to save them?

Because he is a solo maintainer and has an outweighed influence on the software I would depend on. Plasma community is much healthier as a whole.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#297

Post by Joe_Cool »

gf000 wrote: post #217
Joe_Cool wrote: post #178

Earlier quoted context omitted.

You might have an older GPU that doesn't work with wayland like me. My Radeon HD5870 also won't do Vulkan and anything wayland has never worked properly for me.

I'm not questioning what you are saying, but Wayland's only requirement is DRM, which is a Linux kernel capability that is supported for basically everything that you can push some sort of display cable into. It's for buffer management, and X was also ported to use this API. Unless you have proprietary X server blobs, you have mostly the same low level route in either case to display stuff, so it's on the exact compo…

I agree, it should work. It just doesn't. I haven't had the time yet to figure out why it doesn't because everything is fine on X11.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#298

Post by melodyogonna »

strobe wrote: post #284
melodyogonna wrote: post #161

I installed Arch on my old Mac few months ago, alongside Xorg and i3, they were what I was used to before I switched to Mac about 6 years ago. Back then Wayland was a mess, so I never even bothered to check it out this time. However, few days ago my non-technical girlfriend wanted to use my laptop, I couldn't see her using i3 so I decided to install Plasma, a proper desktop environment. Lo and behold I couldn't launc…

I recently had opposite experience - I been using NixOS with X11+i3 for about 2 years and never had any significant issues beside some troubles with one Nvidia driver version, even most Steam games worked for me without any issues. But out of curiosity decided to give try Wayland+Sway. First Sway remind me that Nvidia GPU completely unsupported and probably wont work at all, but in really fix for that just to use som…

Interesting. From looking into it Wayland had issues with Nvidia, I thought that was already fixed? I admit, it is a bit of a hack getting screen-sharing to work; I've not really had time for it yet as it isn't a daily driver for me.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#299

Post by falsaberN1 »

tmtvl wrote: post #241
HiPhish wrote: post #130

I really miss the ability to swap out KWin for a tiling window manager. I'm currently using Krohnkite and it's OK, much better than nothing, but after having used a real tiling window manager the difference is just too jarring. I physically need a desktop which is usable as much as possible both with the mouse and with the keyboard so I have to switch as rarely between the two as possible. Plasma on X11 with a tiling…

Have you tried LXQt? It made things easy for me when Plasma 6 broke a KWin script I was using to improve the multihead experience.

I use LXQt with virtual machines, is it good for using on bare metal too?

Re: Preparing for KDE Plasma's Last X11-Supported Release

#300

Post by gmueckl »

thesuitonym wrote: post #291
gmueckl wrote: post #170

Earlier quoted context omitted.

How many buttons do you want on a window frame then? The typical 4 buttons already take a lot of space in the title bar. Not everything that seems like a good idea at first glance is actually good design.

I don't know man, everybody is fine with putting tabs, and searchbars, and a bunch of other shit in the titlebar, but god forbid we put one button that's actually incredibly useful.

Try to move a browser window when you have 20+ tabs open. This is an incredibly bad UX.
Post reply on HN