Re: KDE4

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: KDE4
by Aaron J. Seigo on Sunday 06/Jan/2008, @16:58

the jumps are due to the compositing. this happens with compiz, too. it bugs the HECK out of me as well. i'm not sure what the solution will end up being, but apparently composition managers do not deal well with canvasy apps like plasma.

when i run a non-compositing window manager things are silky smooth.

blarg.

you have no idea (or.. maybe you do =) how frustrating it is after compiz and what not having been out there for the last few years how much composite, argb, etc support in x.org and its drivers just flat out *sucks*.

it's The Way for the future (non-composited displays just won't be around in years to come, i'm sure of it; there are too many advantages) so we shouldn't deviate .... but i wish x.org was a bit more ... robust in the area.

nvidia's new driver they released at the end of december works properly with argb, though! hooray for the small wins =) and that's exactly how it's like to go; a lot of my near future will consist of trying to find ways to stack up more and more of these little wins by exposing the weaknesses and working with those responsible for those pieces of software to address the issues. not exactly my idea of "fun", but .. yeah. needs to get done.

Related Links

·   Articles on KDE in the News
·   Also by Aaron J. Seigo
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: KDE4
by T on Monday 07/Jan/2008, @01:05

Just as KDE apps were needed to help insure that the KDElibs are really "ready," so too I guess KDE is going to help make x.org "ready." While it surely will be a challenging/annoying road, we'll be grateful in the end!

[ Reply To This | View ]

Re: KDE4
by Jeff Strehlow on Monday 07/Jan/2008, @21:04

"it's The Way for the future (non-composited displays just won't be around in years to come, i'm sure of it; there are too many advantages) so we shouldn't deviate"

But doesn't composting slow things down and take up a lot of memory? To me those are huge disadvantages. I sure hope it will be possible to turn it off or better yet put it in a separate package that can be uninstalled if we don't want it; that way there wont be code sitting in memory that isn't used for anything. I'm sure there are a lot of people out there that don't have the latest computers (like my wife) and won't use KDE4 if it makes their computer run much slower.

[ Reply To This | View ]

Re: KDE4
by Paul Eggleton on Monday 07/Jan/2008, @22:52

Of course you can turn it off.

[ Reply To This | View ]

Re: KDE4
by jos poortvliet on Tuesday 08/Jan/2008, @02:37

well, compositing does those things now, but theoretically, it should actually speed up things. "Just" needs a proper X.org and driver architecture, which we simply don't have right now...

[ Reply To This | View ]

Re: KDE4
by reihal on Wednesday 09/Jan/2008, @03:30

And we never will, unless KDE and/or Trolltech takes over it.
The division of Linux, X and KDE is the way that MS can "conquer by division".

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"Ahhh, the whole screen feels bigger now." -- Waldo Bastian
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.