Slashdot Mirror
Gnome 2.2 Released
heydrick writes "This message confirms that Gnome 2.2 is officially released. And a month ahead of the originally planned six-month release cycle. Check out the Gnome 2.2 Start Page and use a mirror to download."
← Back to Stories (view on slashdot.org)
Thanks to all the developers who have really put in to get this release out the door - it looks unreal!
2 /
For those who have not already, check out the screenshots http://vhost.dulug.duke.edu/~louie/screenshots/2.
The final license stuff is still being taken care of by the board. It's been a year in negotation; we didn't want to rush or hurry that just for one release.
IAAL,BIANLY
No they are talking about xalf which had many problems. Startup notification is a freedesktop.org spec so KDE and Gnome apps should be using this, at least in the future. (I'm not sure how much KDE has jumped onboard freedesktop.org standards).
Yes. The KDE system was a good first attempt, but suffered from not having toolkit/desktop integration as well as it could have. If an app didn't support it, or crashed on startup, the throbber would hang indefinately. This system has toolkit/X integration, and is only activated for programs that flag themselves as supporting it, so it's more robust and useful.
here
there is a gnome-vfs addon that supports ssh. its part of gnome-vfs-extras, I think.
The new file selector will be implemented in GTK 2.4
"I keep looking in the want-ads under 'revolutionary' but there don't seem to be any listings.. "
And here you are:
http://people.debian.org/~walters/gnome2.html
I'm personally running the Sid version, which works great with a few minor quirks (Rep hangs on occasion and needs a good -HUP spanking), nothing horrible to deal with. There are also unnoffical Woody packages, if that's your bag.
Enjoy!
El riesgo vive siempre!
Crispin
You can turn off all desktop icons from the preferences dialog in Nautilus.
Eddy.WriteLinux.Com
Here, from Havoc
Here, from jdub
There is a list for GTK2.4 on the website, but unfortunately I think GTK2.4 won't be ready in time for GNOME2.4, so 2.4 will still be based on GTK2.2
From 'Back To The Future' movies - it's Doc's line. :-)
Anyway, nice work GNOME team - now, to the future!
zWhat would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
The key is:
Note that this will only effect gnome2 apps (I think). If your gnome1 apps have tearoff turned off you have to use the old gnome-cc to enable. Also, don't be afraid of gconf-editor, a good number of the so called "missing features" are still there!
Well, a new file dialog is planned for GTK2.4, and is developing in libegg CVS.
Note a few things:
1) GTK is a separate project from GNOME. That means, it's not simply something the gnome team have forgotten to get around to, it has to fit into the gtk feature cycle, it has to go through usability reviews, it has to be tested etc. New APIs will be needed probably. Then it has to be integrated with standardised mime typing and so on. There's a lot more work than you might think.
2) For GNOME2.2, gtk2.2 was released in time, great, fab. That probably won't be the case for gtk2.4, for reasons I won't go into, but basically the release schedules just don't mesh. However, GTK2.4 is backwards compatable with 2.2, so when it does come out, you just drop it in - all the apps get the new dialog.
The file selector does suck, but it takes more than a month for us to implement a good one. When it comes, it will rock, but since it should have a stable API for a long time we want to get this done right. The file selector will be in Gtk 2.4, releasing in September. At this point you can drop the new Gtk library into place and all Gtk programs will have the new file selector.
Are you lying? Have you last used KDE in 1997?
You are wrong.
The (configurable) throbber will quit no matter what happens after 30 seconds.
I have yet to find an application that does not "SUPPORT" KDE startup notification. Netscape, Mozilla, all GNOME and KDE apps, OpenOffice, AcrobatReader, gv and lyx all support it.
Are you telling me that the GNOME startup notification will work only with GNOME apps and that it is more "robust and useful" because of this? I can't believe it.
Are there really any technical differences? AAFAICS, both GNOME and KDE agreed on a common protocol for X11 startup notification support:
0 02 -October/000801.html
https://listman.redhat.com/pipermail/xdg-list/2
Moritz
Like the idea of 2.2, and want to know if it works?
Don't want to have to compile a practically infinite number of packages from scratch by downloading each... and... every... one?
Don't want to trash your system by overwriting tons of libraries?
Don't trust your local package management system (or the packagers for that matter) to back out once you upgrade?
Check out Garnome. It's easy to download and install, and best of all, it installs under your home directory by default! They have a good walk-through on the main page. I've found this to be very nice, and a far smoother testing mechansim than anything else out there!
You just download a small BSD-style ports tree, and then kick off a compile (follow the README). It downloads, compiles and installs everything else!
They "got around" this by taking a shot of the root window and bluring. But I don't know what "strange effects" you're talking about. In general, the technique works well, but deffinately falls under the "hack" category. The *real* solution would be to use XRender, but well, that's a-whole-nother ball of wax that I don't want to get into.
Let's hope that there's intelligent life somewhere out in space 'Cause there's bugger-all down here on Earth.
I think you must have a bad build or something. The general experience is that Gnome and the current Nautilus are much faster than the 1.x versions. They definitely are for me, anyway.
There have been some complaints about gconf acting like the windows-registry system. I might as well address them here. Now I dislike the windows registry as much as you do, but please do not label gconf as "evil" before you check out what it really does and what it really can do. The registry-like system was not neccessarily evil by itself, but MS implemented it such that it was hell to use. Remember why you started hating it?
;-p
;-p
1. A slight misconfiguration usually leads to unusable systems and needs a reinstallation
2. Too many things (including system level configuration) are integrated with it
3. Stored in a big binary chunk that no other application can read without using the windows API
4. Little to no documentation for most keys
5. Made by M$
Now gconf has none of these flaws:
1. Any misconfiguration that (if even possible) renders the GUI unusable, and you can still use the CLI or a text editor to undo / fix your changes.
2. no system critical processes depend on it
3. stored in XML format
4. most key names are self-explanatory, and there are places where comments about the keys can be written
5. Completely open source
In addition, gconf has the feature that appplications using it are informed of updates to the configuration immediately, so it won't require a restart of the application for things to take effect, while for the windows registry, the application has to poll the registry for changes if it wants to know whether things have been changed.
The "traditional" convention for unix apps was that every app had its own configuration file format, located in anywhere that the developers pleased, and they wrote a config file parser only for their own app. This is a huge waste of time and resources, where developers could have spent their time better in improving their apps instead of worrying about config file formats and writing parsers. Now gconf solves these issues and in addition gives the application a bunch of other features. What more could you ask for?
Don't quote me on this.
AFAIK, this was the case also for gnome 1.4 and maybe in gnome 1.2. The funny-looking file names maybe were placed in a different place: try looking in your ~/.gnome* directories.
The main difference between 1.4 and 2.x is IMO the user target: 1.4 was a nice tool to hack a very customised desktop on your PC. With 2.x, they try to reach the standard computer users, hiding away most of the options and implementing the hints of some 'usability studies' they have done with Sun (of which the 'Action' menu is I think a result).
Ciao
----
FB