| |||||||||||||
Composite toggling in gnome3Composite toggling in gnome3Posted Feb 8, 2012 13:31 UTC (Wed) by jriddell (subscriber, #3916)In reply to: Composite toggling in gnome3 by mjg59 Parent article: Canonical pulls funding from Kubuntu
"Expecting applications to fall back gracefully"
That's what Qt and Qt Quick (QML) does really well, it's one reason why Canonical are becoming Qt fans. KWin does it great too.
(Log in to post comments)
Composite toggling in gnome3 Posted Feb 8, 2012 13:41 UTC (Wed) by mjg59 (subscriber, #23239) [Link]
And the application that's drawing translucent or transformed windows as part of its functionality suddenly finds that things don't work. Compositing isn't just about pretty effects. It's an entirely reasonable design decision to depend on aspects of it, possibly with a static fallback in order to support running in a legacy environment. But asking applications to support modifying their UI at runtime just so someone can get a few more FPS in a windowed game? That's ridiculous.
Composite toggling in gnome3 Posted Feb 11, 2012 13:48 UTC (Sat) by jospoortvliet (subscriber, #33164) [Link]
Again, as Riddel said, Qt/QML apps can do that quite well. Look at KDE's Plasma - does the same thing. Disable compositing and the desktop adjusts to the new situation, replacing the artwork to fit a non-composited environment. I don't see why you wouldn't want apps to do that... If you use a crappy toolkit that makes it hard, fix the toolkit or use something else :D
|
|||||||||||||