User login

Navigation

Contribute

Interested in contributing to FootNotes? Click here to submit news stories to us or visit this site for more information about available opportunities.

Art.GNOME.org

Error: It's not possible to reach RSS file...

GNOME Support

Friends of GNOME

Now's a good time to say thanks for the best desktop environment on the planet by becoming a Friend of GNOME or by upping your current Friends level. Contribute by joining the Friends of GNOME program. All contributions are tax-deductible in the U.S. Thanks to our generous Friends

Links of Interest

Syndicate

GNOME 2.22 released

Submitted by bolsh on Thu, 2008-03-13 07:02. GNOME

GNOME 2.22 has been released, bringing a whole ream of new apps, features and improvements to GNOME users.

Among the most significant additions in this release are the addition of a photo and video taking application that integrates with your webcam called Cheese, a new VNC viewer called Vinagre and the addition of an advanced and integrated IDE, Anjuta.

Notable improvements are the improved support for DVD playback, subtitles and VLC support in the Totem video player, an improved international clock applet, Google calendar integration in Evolution, improved accessibility for web apps and a whole new library to support networked file-systems.

compositing and hardware acceleration

Submitted by Anonymous George (not verified) on Tue, 2008-03-18 16:18.

As far as I know, there are two compositing techniques:
1) XRender based (xcompmgr, KDE-3, KDE-4, Xfce, ...)
2) OpenGL based (Compiz, Beryl, KDE-4)
Both can be hardware accelerated. However, drivers developers are typically focussed on OpenGL acceleration. Nevertheless, NVidia proprietary drivers do hardware accelerated XRender extension, and xcompmgr in NVidia cards is really very fast. XCompmgr is also quite fast at vesa driver!.
Some drivers (SIS) used not to accelerate the Xcompmgr operations thought -perhaps they do not implement any acceleration for XRender operations-. I had a SIS-based laptop and the driver was a pain, because the developer had no info from SIS and had to fight with different cards so he was very busy to achieve the kind of refinements required to accelerate XRender. He only could accelerate OpenGL in one of the models. The work of that guy was incredibly good, don't take me wrong, but the driver was not at the level of NVidia's or Intel's - hardware was not anyway.

» parent