| |||||||||||||
Vignatti: X on WaylandVignatti: X on WaylandPosted Jun 15, 2012 19:44 UTC (Fri) by cmm (guest, #81305)In reply to: Vignatti: X on Wayland by nix Parent article: Vignatti: X on Wayland
> Because the world would have been a *better* place without fvwm, gwm, KWin, compiz, XMonad, Awesome and dwm
as painful as it is for me, as an Awesome user, to claim: yes, it would probably be a much better place.
copy/paste would _work_. there would be some logic and theme in the window-management keyboard shortcuts. applications with long-standing window-management brokenness (try using OpenOffice under Awesome, for instance, or pretty much any Java GUI program) would be unthinkable. I would not have to suffer video tearing on my allegedly well-supported Intel graphics chip, because everyone's environment would be similar enough for this buggy behavior to be universally irritating (providing sufficient motivation for the developers of whatever responsible part to bloody well fix it already). stuff that actually matters would work better.
(Log in to post comments)
Vignatti: X on Wayland Posted Jun 15, 2012 19:54 UTC (Fri) by nix (subscriber, #2304) [Link]
Why on earth does everyone say copy/paste doesn't work? It works exactly as well as it does on Windows, which is to say perfectly well iff you're copying something vaguely textual and both apps are still running. Shut the source app down and what you get back might not look quite as good as it did before.
You know how many people I've heard complain about this behaviour, outside this thread, in my entire life? Zero. Nobody other than geeks even *notices* it.
(As for the video tearing, well, that's something else I've never seen, and is not something that wiring policy into the graphics server would do -- or, rather, its existence is merely a consequence of the sort of transition -- to composition -- which is pretty much entirely impossible to implement if you nail lots of policy into the graphics server.)
Vignatti: X on Wayland Posted Jun 19, 2012 12:52 UTC (Tue) by nye (guest, #51576) [Link]
>Why on earth does everyone say copy/paste doesn't work? It works exactly as well as it does on Windows, which is to say perfectly well iff you're copying something vaguely textual and both apps are still running.
Well, there do still seem to be problems with copy/paste in my recent experience.
What I want:
What I have:
Strictly speaking, X is not at fault here. There's something going wrong with Klipper, or KDE, or Qt, or GTK, or some specific combination thereof, but that's sort of the problem - if X specified a policy, there would be much less scope for those things to introduce bugs/incompatibilities/design disagreements.
That's not to say necessarily that the answer truly is to wire a lot of policy into the display server (for one thing, it's probably too late - any attempts to improve the situation by adding more policy risk creating *more* incompatible combinations), but there is a real issue there.
Vignatti: X on Wayland Posted Jun 19, 2012 20:31 UTC (Tue) by hummassa (subscriber, #307) [Link]
I am a heavy KDE user (at least 10h/day, 300 days/year) since 1998. I never ever had a problem within the requirements you describe. I only discovered that you must keep the "from" app running (WRT not losing text formatting) when this thread started... Probably I never had closed the "from" application before. :-D
Vignatti: X on Wayland Posted Jun 20, 2012 12:43 UTC (Wed) by nye (guest, #51576) [Link]
I do have some use cases which are probably rather atypical. I'm going to try to remember to keep a log of when paste does something unexpected. Maybe there are some specific applications triggering it that I've just never noticed.
|
|||||||||||||