"Back in November we started sharing some of the exciting features planned for the GNOME 2.22 and 2.24 releases, and now that the first GNOME 2.22.0 Beta release is planned for later this week, we have taken another look at the packages set for inclusion and the changes that have actually been made. While nothing groundbreaking will be introduced in GNOME 2.22, this desktop environment does have some moderate changes worth noting. In this article are eight interesting packages that either have noticeable changes since GNOME 2.20 or are new to GNOME. This list isn't all-inclusive or ordered in any particular fashion, but just eight changes that had caught our attention."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-06
GVFS/GIO are bottom-up rewrites of GnomeVFS by Alexander Larsson, I believe.
In a nutshell, GnomeVFS is one big, ugly hack. It's not very abstract, yet its place in the stack implies it's a high-level library ("gnome-*" librares are only useful in Gnome apps, not GTK or merely GLib apps). It's got a pretty crappy API (inconsistent, very few utilty functions, too dependent on Unix-isms). Many backends are broken and will bring down your whole app unexpectedly. It relies very heavily on the Unix filesystem model (too much for a VFS). It lacks such basics as atomicity, state (!!!), or a GObject-based model.
It was desperately in need of a rewrite.
GVFS will exist in the right place in the stack (GLib, the basic, framework libraries upon which others are built). It will have a generalized, abstract API. It will use GObject (this makes it easier to wrap for other languages, or use in an OO way in your GTK/GLib app). It will maintain state (for authentication, caching, data sharing, connection maintenance, etc). And perhaps most importantly, backends will no longer be in-process (they can't crash your app if they go down).
So yes, it is big, and it is cool. I, for one, can't wait.
Member since:2005-10-02
Because Gecko doesn't work well. It's that simple. Webkit is much faster and more stable and uses less memory and is more portable, and better suited for embedded projects - not to mention computers that are not quite modern (like mine).
And because Firefox and Thunderbird are not well integrated on Linux at all.
Member since:2005-11-21
Just as GNOME runs on several kernels, can use several audio APIs and can use several X servers, it can also now use several rendering engines. Apple didn't even "develop their own" rendering engine, they're using a modified version of KHTML.
Back to the article: there is a brief mentioning of GVFS. "VFS is the new GNOME virtual file-system." That seems like quite an important change. Anyone know what that brings to the table?
If you have bothered to take a look at the WebKit branch you'll discover that the KHTML engine Apple forked has advanced in countless levels within that project to a point where it's not only reinvented itself but expanded in scope far beyond what the KDE project has developed for it.
Member since:
2006-01-04
Firstly I assume that when Firefox 3/Gecko 1.9 is released with the look-and-feel updates, Epiphany with the gecko back-end will support native widgets. Secondly, so long as Epiphany works well, why do they need to make their own rendering engine?
Just as GNOME runs on several kernels, can use several audio APIs and can use several X servers, it can also now use several rendering engines. Apple didn't even "develop their own" rendering engine, they're using a modified version of KHTML.
Back to the article: there is a brief mentioning of GVFS. "VFS is the new GNOME virtual file-system." That seems like quite an important change. Anyone know what that brings to the table?