Maybe we could summarize those things that he have agreed on and post them, maybe on a different thread, to clear up all the chatting here and start fresh.

andreas_k wrote:For the overview I added an side panel (optional).


And for the modules I make a new mockup.

Header, Description and preview on top. I made the preview on top, because this three parts are shown independent from the settings. So the user know I make the settings for the modul, with the preview of the selected setting.
In tabs the Selection part and the Configuration part. I also look at the modules of the existing SystemSettings. There are two possibilities of Configuration grouping:
1. Each configuration section has there own tab
2. The configuration settings are grouped in blocks

To get an better overview the groups are better but than you have all settings on one page. If you make tabs you can separate into the main settings and advanced settings quite easy.

I look at all existing moduls and the style could be used at every modul. Some moduls use portrait previews (emotions, font management). At this few moduls the preview is on the right section.

These are quite nice andreas_k. They appear to comply with the HIG layout and typography guidelines and represent a nice freshening of the current system settings design that respects the previously agreed upon content structure, and has the benefit of looking and feeling familiar. There are probably a few bits here and there to refine (see Heiko's comment) but, IMHO, this may be the most practical approach to the systemsettings redesign I've seen so far. I'm of the opinion that we take your proposal as the post-brainstorm starting point, and proceed with refining it towards a final proposal in a separate thread.

If I had 10 thumbs I'd put them all up!

P.S. I'm aware that some kcms are unlikely to be redesigned (window decoration kcm for example), so my comments above are mostly about the elements of the mockups related to the systemsettings app, not the kcms.

Heiko Tietze wrote:Your proposal looks clean and usable. But didn't we decide to introduce scrolling content instead of a breadcrumb? And as far as I remember a premise was to get rid of tabs.
Anyway, it's a nice what-if experiment.

I'll think of it. Thanks for the information. Maybe you can post the results of the system settings brainstorming. The good thing of using tabs is that you can have one tab for select the second for changing the settings and the third tab for detail changings. so you can group the settings and don't have to make buttons for detailed settings every time. I want to remove the buttons.

Can anybody give me feedback if it is possible to have the import, export icons in the iconbar individual for each kcm module?

Ok I talk to Heiko and now I know where the system settings journey should go.

No Tabs use Grouping with Scrollbars. The navigation should also use scrollareas (http://user-prompt.com/de/kde-system-se ... avigation/).

A mockup for the Window Decoration modul. I don't want to talk about the sidebar (navigation) there is another thread.

Structure of the modul
- Header
- Description
- Preview
- Simple settings (advanced settings via button, additional user input)

at the window decoration the realization of this structure is quite easy. the user have a preview of the window decoration and on bottom a selection area where the user can select or import/export additional window decorations. with the icon bar buttons the detailed configuration of the decoration and icons is possible. the detail configuration depend on the selected window decoration. some decoration support less configuration, .... So the user have to select in an first step the needed decoration and if the user wanted to change the selected decoration it is possible via an button. simple for standard use, powerful via an additional click.




If you like the idea I can make a mockup of an more complex module.

I really like these mockups:



Two little issues:

1 - aren't the 'Configure Decorations' & 'Configure Buttons' buttons kind of mimicing the behaviour of tabs, doesn't the HIG say something to the effect of 'don't use non-tab elements to simulate tabs'?? Personally, i think in this case they work well & maybe what we should do is define in the HIG how 'things that are a bit like tabs' should & shouldn't be used (& when they're appropriate), rather than just saying 'avoid things that are anything like tabs'.

2 - Those 'Configure Decorations' & 'Configure Buttons' buttons at first glance could be mistaken for breadcrumbs (they're similar to the breadcrumbs in Gnome Nautilus/Files), they might be better moved away from the 'System settings - 38 Moduls' button on the top left - maybe in this case they'd work below the preview in the content area (about a 1/4 of the way down). That makes them more like tabs but i think if tabs-like-things are going to exist then that's an appropriate use for them & they could work well.

ken300 wrote:Two little issues:
1 - aren't the 'Configure Decorations' & 'Configure Buttons' buttons kind of mimicing the behaviour of tabs, doesn't the HIG say something to the effect of 'don't use non-tab elements to simulate tabs'?? Personally, i think in this case they work well & maybe what we should do is define in the HIG how 'things that are a bit like tabs' should & shouldn't be used (& when they're appropriate), rather than just saying 'avoid things that are anything like tabs'.
2 - Those 'Configure Decorations' & 'Configure Buttons' buttons at first glance could be mistaken for breadcrumbs (they're similar to the breadcrumbs in Gnome Nautilus/Files), they might be better moved away from the 'System settings - 38 Moduls' button on the top left - maybe in this case they'd work below the preview in the content area (about a 1/4 of the way down). That makes them more like tabs but i think if tabs-like-things are going to exist then that's an appropriate use for them & they could work well.

Good explanation. The buttons should be below the preview area and the buttons are not tabs, because you have select first, what you want to configure (which window decoration) and than you can edit them, like an advanced settings button.

I have a problem with the icon bar on top. I want to have an icon bar, because for the overview page I need the search bar on top and to have a consistent workflow I'll also have an icon bar for the modules, but I don't know which information I should implement there. Only for System Settings, or a back button I don't need the icon bar. The system settings could also be in the side panel. So maybe It would be a better idea to remove the icon bar?



I think now it is more clear. in the side bar there is the navigation and on the main frame the settings. on bottom the standard buttons. Like it.

andreas_k wrote:A mockup for the Window Decoration modul...

My first impression was: Why should I reverse my workflow from left/right and up/down? First I have to select the preset (Breeze decoration) and then click Configure above to modify the details. But after thinking a while about your solution I see the advantages. So it's quite clear what you actually configure because the preset selection is not shown anymore. But I wouldn't adopt Configure to the current selection with the need to specify it with decoration/button. It could rather be called Configure or Advanced and show all options on click.
Edit: It's much better to place the buttons below the content as you did in the last mockup. Looks good now.

Appologies for my misunderstanding - this looks great:

I have created a new thread here to continue with the refinement of the systemsettings application design: viewtopic.php?f=285&t=124463


Can an admin lock this (very long) thread please? Thanks.