Remote desktop vs. remote display

Posted Feb 21, 2013 6:48 UTC (Thu) by mmarq (guest, #2332)
In reply to: Remote desktop vs. remote display by renox
Parent article: LCA: The ways of Wayland

and sure it isn't the toolkits guys fault... that is a lost battle, ppl should get over it, more so because there is a very simple solution...

* a common Icon engine

* a common theming engine (embeddable) mainly for the "app windows" and doesn't touch panels, docs, bars or special widgets.

Than the battle that is not lost yet, is putt a "common" display engine for everything from boot (Grub DM) to the desktop, one which could take the responsibility for basic multi display, mouse pointer and keyboard (among other things)... it could even be the engine for something like Coreboot setup display and help this one gain traction...

Can a striped down version of Wayland fulfill those rolls, be the "mouse pointer engine" and the "keyboard engine" for the desktop in collaboration with the main windowing system ? ( i think it can)

In debugging or a crash situation of the main desktop, is just a pain why does the keyboard mapping have to change and why does the mouse pointer theme have to change...

Then at least Wayland would be tremendously faster to adopt and evolve... and with those successful... than to port the now ~200.000 X applications allover all this years, to be Wayland apps, and to accomplish that will require ugly buggy and instability prone hacks, of servers on top of servers...

Honestly, i have nothing personally against Wayland... and it hasn't to do with the engine itself (which could be good)... but i couldn't think of a better *mess* than this, to throw Linux desktop back to stage 1.