Linked by on Wed 1st Feb 2006 19:53 UTC
Permalink for comment 92361
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/23/13 17:52 UTC
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
More News »
Sponsored Links



Member since:
2006-01-17
Qt/Arthur doesn't need XGL backend (XGL won't even expose it's own API set). XGL will have hardware accelerated XRender (and even indirect GL), so KDE/Qt won't even know if it is running on XGL or regular XAA/EXA server, it will be accelerated on XGL automatically.
Compositing effects are unrelated to this, KDE people can write their own one easily if needed, although I think there will be joint solution by more UI communities to have common powerful, extensible, flexible, hookable, etc. compositing manager.