Device and Network Independence

Posted Jun 10, 2013 10:48 UTC (Mon) by ortalo (guest, #4654)
Parent article: The Wayland Situation: Facts About X vs. Wayland (Phoronix)

For the sake of preserving LWN's commenters reputation on this topic, I thought we could extend even further than network independence concept for the goold old X13 display server, what about a windowing system that would offer device independence too?
Of course, for the sake of gamers, we may select GL/ES as the language instead of good old Postscript (but I'm still hesitating with the DVI command set for LNCS books reading). Let's have that Wayland *be* the toolkit server, the software that will unify Qt, GTK, DirectX and the like under a single rule (network independently of course.)

Device and Network Independence

Posted Jun 10, 2013 15:17 UTC (Mon) by drag (guest, #31333) [Link] (1 responses)

Wayland is actually the X11 dev's attempting to get out of the toolkit business once and for all. You can imaging GTK and QT as building on the X11 toolkit.

Instead of dictating methods on how Applications should be rendered (which X11 tries to do, and fails) all it cares about is the buffers produced by the application themselves. If the application wants to use OpenGL, DirectX, QT, GTK, or space monkeys with typewriters to render itself it makes little difference as far as Wayland is concerned, ideally.

Device and Network Independence

Posted Jun 11, 2013 8:39 UTC (Tue) by mmarq (guest, #2332) [Link]

Yes X11 could dictate that the window manger should handle it.

Consistent look & feel is important, and it could even use space monkeys. freedom is ok but anarchie is not