Linked by Thom Holwerda on Fri 5th Nov 2010 19:15 UTC, submitted by Debjit
Permalink for comment 448943
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2010-11-06
Network transparency is a useful asset also for home users (gui on a home server). But I still do not think it is a problem in itself that Wayland does not offer network transparency. This functionality should move to the toolkit:
* The amount of data involved in drawing windows has increased tremendously since the X protocol was invented. If I am correct gradient of e.g. a window bar are moved pixel-by-pixel in X. It would be much more bandwidth efficient to move more high level graphics primitives over the network.
* Remote apps integrate awfully in a local work station, even if they use the same toolkit as your local desktop. Themes are often very different.
Moving the network transparency to the toolkit would solve both problems. The downside is of course that more toolkit should offer this functionality. But in my opinion it will be enough if QT and GTK operate over the network. If we are burying old ancient software, lets bury motif as well.