Slashdot Mirror
Next-Gen X Window Rendering For Linux
Bytal writes "Seth Nickel, a GNOME hacker, has an extensive treatment of the next generation Linux graphics technologies being worked on by Red Hat and others. For all those complaining about the current X-Windows/X.org server capabilities, things like 'Indiana Jones buttons that puff out smoothly animated clouds of smoke when you click on them,' 'Workspace switching effects so lavish they make Keynote jealous' and even the mundane 'Hardware accelerated PDF viewers' may be interesting."
I submitted this story to Slashdot last week, but for some reason it seems to be stuck in "Pending" status, so go here: http://nat.org/2005/february/#9-February-2005
It's an OpenGL-based X11 server, complete with some screenshots. Apparently, window dragging is very smooth (no repaint events are even given to the apps), and with Cairo and GTK, this really could be the future backend for Linux desktops.
overall the idea is good, however...
1) rendering to texture is slow on some GPUs, especially GPUs with limited memory.
2) alpha blending is expensive on almost all GPUs.
imo X needs an overhaul, needs to ditch the legacy crap (lose Xaw for example) and move on. stop interfacing with video hardware like it's 1980.
A few things that sound useful, like:
- Hardware accelerated PDF viewers
- Synchronized smooth resizing so there's no disjunct between window borders moving and the contents redrawing (you should see the demos of this in luminocity... it really makes a difference in how real the interface feels, just as double-buffering did for stuff moving)
- A shared path between on-screen display and printing (using Cairo's PDF/PS backends)
- Alpha transparency in applications whenever and wherever the urge strikes us
A couple things that may lead to greater usability:- Toolkit themes that draw with layer blending effects, delightful bezier curves, and irritating alpha gradients
- Live window thumbnails
And lots of rather pointless fancy eye candy:- Indiana Jones buttons that puff out smoothly animated clouds of smoke when you click on them
- Hundreds of spinning soft snowflakes floating over your screen.... without messing up nautilus
- A photograph of a field of long dry savanna grass as your desktop background... where the grass is gently swooshed around by a breeze created by moving your mouse across the background
- Windows that shrink scale and move all over the fucking place with cool animations
- Vector icons with very occasional super subtle animations rendered in realtime...a tiny fly which buzzes around the trash every several minutes, etc... think mood animations as in Riven (which as a total random aside is still a shockingly beautiful and atmospheric game years after it came out, postage stamp sized multimedia videos notwithstanding)
- Workspace switching effects so lavish they make Keynote jealous
- Brush stroke / Sumi-e, tiger striped, and other dynamically rendered themes where every button, every line looks a little different (need to post shots / explanation of this stuff, but another day)
- Progress bars made with tendrils of curves that smoothly twist and squirm like a bucket of snakes as the bar grows
- Text transformed and twisted beyond recognition in a manner both unseemly and cruel
- A 10% opaque giant floating head of tigert overlayed above all the windows and the desktop.
Now, these fancy effects are certainly kind of cool, and may look nice. (Though I can guarantee that when they're all in, I'll probably still be using Blackbox.) However, is that really all that the future holds? More special effects, without any substantial improvements in usability?How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
Um, if it's hardware accelerated, it will be eating fewer of your CPU cycles
Not necessarily so. Well, only if they use hardware acceleration to do existing tasks that are already being done solely by software acceleration. I mean, how many resources does xpdf et al use really?
However, if they are introducing new eye candy wizz-bang GUI magic, chances are that the hardware requirements (including CPU and RAM) will be much higher anyways - even with suitable h/w- accel compatible hardware. And for course those without the h/w-accel compatible hardware, this would eat up even more CPU cycles for the rendering. I repeat, how many resources does xpdf et al use really?