Bug 403918 - Remove Secondary Group
Summary: Remove Secondary Group
Status: RESOLVED MOVED
Alias: None
Product: systemsettings
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL: https://phabricator.kde.org/T8871
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-04 10:48 UTC by andreas_k
Modified: 2019-02-04 13:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Calc file (19.79 KB, application/vnd.oasis.opendocument.spreadsheet)
2019-02-04 10:54 UTC, andreas_k
Details

Note You need to log in before you can comment on or make changes to this bug.
Description andreas_k 2019-02-04 10:48:47 UTC
SUMMARY

SySe contain of an Main Group and an Secondary Group before you come to the KCM where you configure stuff.

I understood that KDE has a lot of settings and that's the reason SySe have an main and secondary group. Anyway my proposal is to reduce the secondary group, cause the user have to know in which secondary group an kcm is located to find the correct kcm. But in general the user know what to change and maybe in which kcm it is located, but only an advanced user know in which secondary group the correct kcm is hidden. I use kde a long time and also play a lot with SySe but it's always difficult for me to find the right subgroup.
Comment 1 andreas_k 2019-02-04 10:54:21 UTC
proposal: only Main group and there the kcm's:

1. Appearance (12 kcm's)
   - Look and Feel
   - Plasma Theme
   - Cursors
   - Splash Screen
   - Colors
   - Fonts
   - Font Management
   - Icons
   - Emoticons
   - Widget Style
   - Window Decoration
   - Gnome GTK Application Style

2. Workspace (12 kcm's)
   - Workspace
   - Global Shortcuts
   - Standard Shortcuts
   - Web Shortcuts
   - Custom Shortcuts
   - Login Screen (SDDM)
   - Autostart
   - Background Services
   - Desktop Session
   - Boot Splash
   - File Search
   - Plasma Search

3. Window Manager (10 kcm's)
   - Desktop Effects
   - Screen Edges
   - Touch Screen
   - Screen Locking
   - Virtual Desktops
   - Activities
   - Window Behavior
   - Task Switcher
   - Kwin Scripts
   - Window Rules

4. Personalization (12 kcm's)
   - KDE Wallet
   - User Manager
   - Notifications
   - Language
   - Format
   - Spell Check
   - Date & Time
   - Accessibility
   - Default Applications
   - File Associations
   - Locations
   - Launch Feedback

5. Network (11 kcm's)
   - Connections
   - Proxy
   - Connection Preferences
   - SSL Preferences
   - Cache
   - Cookies
   - Browser Identification
   - Windows Shares
   - Devices
   - Adapters
   - Advanced Settings

6. Hardware (15 kcm's)
   - Keyboard
   - Mouse
   - Joystick
   - Touchpad
   - Display
   - Compositor
   - Gamma
   - Audio Volume
   - Audio and Video
   - Energy Saving (include Advanced Settings)
   - Activity Settings (moved to activity kcm?)
   - KDE Connect
   - Printers
   - Device Actions
   - Digital Camera
   - Removable Devices
Comment 2 andreas_k 2019-02-04 10:54:55 UTC
Created attachment 117827 [details]
Calc file
Comment 3 andreas_k 2019-02-04 10:59:29 UTC
One Main Group was added (Window Manager) and so all main groups have between 10 - 15 kcm's that's a lot when you think on the icon view, but in the sidebar layout you have an list with 12 items in it that's ok.

when you see at gnome settings they show all kcm's in on sidebar, which mean they show also 10 - 15 items in the sidebar. In kde SySe the user can choose first the main group https://blogs.gnome.org/aday/files/2016/01/settings.png
Comment 4 andreas_k 2019-02-04 11:03:05 UTC
There was no rearrangement between different groups it's only the existing arrangement and reduce the subcategory. Sure rearrangement can be usefull. 

From dev point of view SySe is prepared for such a change you only have to define that the first sidebar show the 5 main groups and the secondary sidebar the kcm's in an list.
Comment 5 Nate Graham 2019-02-04 13:11:54 UTC
Strongly agree with removing the second-level, conceptually (implementation requires a lot of merging first IMO).

We are currently discussing a re-organization that would accomplish this in https://phabricator.kde.org/T8871. Let's keep the discussion there.