Xorg and Desktop Eyecandy
BonoLeBonobo writes "Xorg is going to include a new acceleration architecture which will help desktops to have better eye-candy effects thanks to a better XRender, thus composite, acceleration. Developped by Zack Rusin, a KDE and Qt developper, this new feature should be present in Xorg in September. Porting the existing drivers to this new acceleration architecture should be easy."
Because that's what any linux desktop really needs -- more useless eye candy. At least we can look forward to desktop variants of linux looking great well into the future, no matter how much they may suck to use!
-ben
Lounge webcam from c. 1997 http://www.mitwebcam.com/
Who is General Failure? And why is he reading my disk????
The best thing that could happen to X is for it to become ex-.
Try the new edible display from apple - the iCandy!
Some settling may occur during posting.
Before adding further acceleration, how about fix the current problems? Many people have problems with X locking up when using nvidia and RenderAccel (which give a huge speed boost before lock up). When I ask if there is a fix for it, the answer I get is "You shouldn't use it, it's experimental".
Cheers,
RoadkillBunny
In other words, it sounds like you have problems with the way your desktop of choice is configured for AA fonts. Understand that other desktops handle the job quite gracefully and with good results.
Yeah I broke 95 percentile on topcoder but somehow it's my fault that antialiased fonts can be a real bitch in X. Here's a hint: when people say they've tried damn near everything and list most of them and you come back with trivial crap like "select fonts->use antialiasing then "use sub-pixel rendering" when that's exactly what the complaint was, that doing that makes the fonts blurry you just sound dumb.
There are problems with X.org and antialiased fonts. Not every combination of monitor and config has it bad, and some users don't even notice because they have bad vision or nothing to compare to. But when the solution is to edit some XML config file that "it" told you to, and that doesn't even solve the problem, then something needs fixing big time. Do a screenshot of the same page in Win32 Firefox and X11 Firefox sometime and you'll see what I mean.