Slashdot Mirror
GNOME 2.12 Released
Moderator writes "At long last, Gnome 2.12 has been released! Among the many new features are clipboard management, a menu editor, an improved search tool, and a spatial-tree view in Nautilus. Check out the start page for more info."
Link to torrent:n -5.iso.torrent
http://torrent.gnome.org/gnome-livecd-2.12-i386-e
The 'evince' app looks useful, letting you see PDF or some other formats, sort of like the 'preview' app in OSX. But, wait, there's more! As I read the webpage, Evince will now (or will one day) also handle presentation formats (openoffice "impress" and Powerpoint). This last thing is more than just a copy of non-free software, and that in itself is notable. But I think it's more important than that ... I think it would be very helpful to have just one interface for viewing many types of files. Of course, they will have had to make a comfortable and powerful interface; once this gets into Ubuntu or Fedora, I'll have to check it out!
Nah, I agree. There are times when "Yes" and "No" are barely acceptable - namely, when you are asked a very short, simple question by the dialog. But really, if the whole point is to use your computer quickly, even a short dialog should avoid them. Why make the person read a sentence like "The action you are about to perform cannot be undone. Are you sure you want to do this?" in order to figure out what every dialog is for when you can give the familiar user a chance to do things so much more quickly by allowing him to read two buttons - "Delete" and "Cancel", "Delete" and "Don't Delete," something like that. If you are forcing the user to read the dialog in order to know the correct answer, you might as well have buttons labeled A, B, and C, and tell the user what each does in the dialog text.
That said, it's not enough. Prime example: In Quicken (2006 for Mac, anyway), if you are in the middle of the account creation wizard, and click the Cancel button, Quicken pops up a sheet with the usual "Are you sure you want to do this?" type question, and gives you the buttons "Cancel" and "Close." There are plenty of people out there (myself included) whose first instinct is to click the "Cancel" button because Cancel is the first button I clicked and Cancel is what I want to do. Of course, it's also the wrong answer.
I don't mind waiting so much, if it's a heavy app, but I'm really, really annoyed that applications steal back the focus when they finally appear. It's so unintiutive and annoying. Then again, all (or at least the ones I know of) OS:es and managers do this, so it's not specific to Gnome.
:) And if there is a way to get this behaviour today, please please tell me!
If you don't understand what I mean, here's the point: I often start up an application that I will use "in a while" and then proceed to navigate further in Nautilus or whatever. When the app starts, it steals back focus even though I already do something else. That is not usability. There's two use cases:
1. User starts application, waits for it to complete. This would cover almost all common use and especially non-power use. Focus remains with started application from the point that I start it.
2. User starts application, proceeds to give other window focus (by click, ALT-tab, whatever). Starting application at this point loses focus and will not regain it.
Ok, so if the app doesn't steal focus, it may not be obvious that it's finished? That's what the new taskbar hints is for, and it's also a matter of how you behave. Any user likely to have problems with this probably wait for each app to start in turn anyways, so it's not likely to be a problem.
Now this I would like to see. It annoys me at least a couple of times a day.
Spine World
This is fixed in GNOME 2.12 with the exception of starting apps from the terminal (where the problem becomes real complex).
Gnome is the OSX killer.
You are killing right? Its been how many years, better part of a decade and they just added freakin' clipboard services.
Call me back when they:
I've always found that to be interesting, because I'm either stupid, they're cheating, or getting useable fonts in X is just too fucking hard. Much more than it needs to be.
Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
You asked the right person- I care way too much about xcompmgr.
As it is xcompmgr does not have really active development. Pretty much the "final version" was released and is in Ubuntu....but that does not mean nothing has happened. You have two options:
1. (the one I recommend) I am using Breezy right now and I can say that it works much better with xcompmgr than before. The biggest bug for me- artifacts when playing full screen video- is gone in Totem-xine. GONE! The only xine to do that. Its what I really wanted for Christmas. The other bug- the log out screen one- still exists but I have found an elegant work around. Using these directions you can create a panel button to turn it off and on (no crashing). So just turn it off before you log out. Because Breezy likes xcompgr more (the developers were nice and compiled Gnome 2.12's Metacity without its featureless compmgr like they did in Hoary because they heard my begging-it helps to be the second biggest poster in the forum) I found a way to make it stable for you. If I remember correctly you did not like the fading trick, right? Thats awesome for you. Run xcompmgr with this command:
xcompmgr -n
and it will just use the GPU. No tricks, no crashing (me and another Ubuntu fan hammered on this and with just that option it was very stable compared to the fading and drop shadow options)....it just flys! I personally don't do that command (I love the fading) and so I have to deal with some random crashes-much less than Hoary though. You are lucky you do not. Then you must make it start when Gnome starts (go to "System," the "Preferences," then "Sessions." Click the last tab and hit "Add" and the "xcompmgr -n" command and run it in "order 48" -thats what I do, some say use "0" but that only worked for me in Hoary, not Breezy). I must admit that when it boots the desktop might be a little out of focus (or really out of focus with a little garbage) but as soon as you maximize a window everything works like a charm.
2. Use KDE. KDE forked xcompmgr and integrated it into its Window Manager. If you have your xorg file set up, then it gives you a "transparency" tab in the "window decoration" settings box. Its cool, and I hear a lot of the effects (like the fading and such) will be more stable by 3.5. The Gnome guys seem to refuse to do anymore than make Gnome work with xcompmgr because it requires non-OSS drivers to work (Gnome was started because of such strong principles). But since you don't ask much (in the way of effects)...either way will work for you. As you can tell, I care a lot...and the Gnome approach is enough for me for now...
Open Source Sushi
Someone wrote that GNOME is an OSX killer before.
Well yeah, maybe in 2020.
You see, Nautilus alone is vastly inferior to Finder (the new one). Of all gnome components, nautilus is the one that sucks most. Try browsing a large directory with thousands of files with nautilus, konqueror and windows explorer. The latter ones scan the directory MUCH faster. Nautilus takes about 1-2 MINUTES - unacceptable.
The main point of new gnome bugfix releases should be to improve nautilus. Speed it up, say, to about 100 times its current "speed".
Also, it is evident that once an ORDINARY USER (no hacker, no power user, no admin, no dev) has to edit a config file, the whole design has failed. Of course, this is not gnomes problem alone, but to a great deal the underlying OS; however, we are talking about an OSX killer, right? If you aren't lucky, and the hardware doesn't fit 1:1 with the distro, you have to dig through obscure manpages.
I also read that anyone that is not able to edit configfiles is an idiot and everyone MUST learn how to do this. See, I doubt a biologist that made some photos about a weird plant and want to download them from his cam to his PC is interested in editing config files just to get this to work - he JUST WANTS TO DO HIS JOB and is certainly not interested in learning sh and all about the Unix architecture. Config files per se are ok, as long as editing them is optional. Unfortunately, it still is mandatory sometimes (fortunately, the camera issue is resolved automatically by modern distros - but still, simple samba shares have to be edited by hand for example).
This sig does not contain any SCO code.