After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 534000 - Preferences categories
Preferences categories
Status: RESOLVED DUPLICATE of bug 337428
Product: gnome-menus
Classification: Core
Component: layout
git master
Other Linux
: Normal normal
: ---
Assigned To: gnome-menus dummy account
gnome-menus dummy account
Depends on:
Blocks:
 
 
Reported: 2008-05-20 09:05 UTC by Michael Monreal
Modified: 2009-06-20 22:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Attachments
Screenshot (245.88 KB, image/png)
2008-05-20 09:08 UTC, Michael Monreal 		Details

Description Michael Monreal 2008-05-20 09:05:43 UTC 
For some time there has been work to reduce the number of capplets inside the preferences menu. But at the end of the day a normal user will still find 20-25 entries in this menu which is too much.

IMHO Fedora does the right thing and places the launchers into subcategories like Personal, Look&Feel, Network and Hardware. I recently tested Fedora9 and found these subcategories to really help me find the capplet I was looking for faster. Maybe this could be a nice addition for upstream as well?
Comment 1 Michael Monreal 2008-05-20 09:08:17 UTC 
Created attachment 111211 [details]
Screenshot

This is a screenshot from Ubuntu, which uses the upstream menu layout. It shows the massive amount of launchers in preference. If you don't know the exact name of the launcher, finding what you are looking for can take some time, as you most likely will scan up and down the list quickly some times.
Comment 2 Vincent Untz 2008-11-27 02:16:25 UTC 
That's also what we do in openSUSE (although we have System instead of Network there). Probably makes sense to do this upstream, indeed.
Comment 3 Vincent Untz 2009-06-20 22:35:31 UTC 
We have another bug to track this.

*** This bug has been marked as a duplicate of 337428 ***