Post a Comment
But I can't believe Gnome hasn't had this for a while now. As an Ubuntu user I just assumed it was already in Gnome by default. Have users of other distros been editing files in /usr/share/applications all this time? Or maybe other distros included Alacarte as well?
Also I think the older menu editor was dropped five releases ago, not five years ago as the article says.
Hope you're sitting down, this may frighten and shock you but... Some of us actually prefer it!
I didn't mind doing it from the command line so much myself, but this being the 'make everything easy and don't confuse anyone' desktop that Gnome is, you'd think they'd have done something about this awhile ago.
I've always wondered why they didn't copy the old method of a series of directories and links where the user creates and modifies it completely ad hoc using, dragon droppings, modifying already familiar primitive objects. Runtime too slow take that finished directory structure as an intermediate and generate some other format to read... it's still good.
I often customize my menus, but mostly to remove unneeded entries from there. For example, why would I want to have an entry for Bug Buddy there when I never actually use it? I don't even know what to exactly use it for, except for situations when an app crashes, Bug Buddy pops up to annoy me. I haven't had to add any new entries, though. Just removing all the unnecessary clutter is enough for me. Oh, I did modify the beagle launcher to make beagle do a tray icon. By default it didn't, which IMHO is stupid. Anyway, a menu editor is a good thing to have. Even Windows 95 had it...
If you happen to install something outside of your distributions default package manager, usually the only way to get it into the menu is through the use of a menu-editor, if you install through apt-get or a series of scripts, automatix for example, they usually take care of all of this in the background.
IMO, Alacarte isn't there yet. Not only is it slow, but editing your menu should be as simple as clicking on the menu entry and selecting "properties" with the option to rename, change paths, remove from menu, move to another subfolder, change icon, etc. Not having to fire up a whole other application which then loads all your menu entries again, at which time you have to again find the menu item you were interested in.
Adding/removing/editng Gnome menu items should be as simple as adding/removing/editing Gnome panel items. Why not use the same procedure for both? This is one area where I feel Gnome just hasn't got it right yet.
I see very litle reason to edit the menu. I think I may have once edited the menu using some new toy software from gnome-files, but the novelty of it quickly diminished. The menu in Gnome isn't like the start menu in Windows--it doesn't get cluttered like mad.
So I wonder why so many people want to be able to edit the menu so badly?
So I wonder why so many people want to be able to edit the menu so badly?
Curiosity, mostly. Everybody knows how in Windows. I first thought it couldn't be done in Linux. It took me years to stumble across fd.o and see how it's done - and even longer to install Ubuntu and see Alacarte...
Well, usually what happens with a new Gnome release is that at x.x.0 it is a feature release, then you have x.x.1, x.x.2, etc. Those are bug fix releases. For example, in Debian Sid, the current Gnome release is 2.14.3. Which is more than likely the last of the 2.14.x versions to be released, but it's very stable. Hopefully 2.16.1 will be out and packaged for Etch before it's final release in December.
I'm sure Ubuntu and hopefully other distributions will have the 2.16.x releases as well, and not just sit at 2.16.0.
I have had problems with the latest release of Gnome with it dieing and restarting. The menu is the least of the worries for Gnome, I wish they would focus on stability and getting the bugs worked out.
What system are you using? How are you measuring performance?
The menu is getting a lot of attention in which I do not feel it needs.
By the press, absolutely.




