Created attachment 109496 [details]
properties tab mockup
Two months back i was working on the a new simplified mockup for the properties tab/pane of the sidebar and the discussion behind it can be found in the design team's redmine forum < https://redmine.documentfoundation.org/boards/1/topics/69 >. It seems that i forgot to file a bug for it. :D
The basics of it are:
1) The sections are divide in a manner easily understood by users, rather than according to the properties found in the character, paragraph and page dialogs.
2) By default, advanced features are not shown in order not to overwhelm the regular user with more features than they normally use, but these features can easily be unhidden when needed by clicking on a button at the bottom of each section which looks similar to the show sidebar button (attachment 105798 [details]).
3) Large 24x24 icons are used for easier identification and them having more clickable space, as the sidebar has more than ample spacing when compared to the toolbars. (my son's netbook screenshot - attachment 105107 [details])
After taking a first look at it I would like to say that I like it already.
Regarding point 2: This is very good, but where can I find this button in the mockup? You wrote it is at the bottom of each section. Or do you mean with this the already existing button at the top right of each section? Your link to the button screenshot looks at my computer unfortunately a little bit weird.
Is the Page section folded as standard?
In the section Lists can I there also change between Numbering and Bullets and what will open with the Graphics drop-down list? Is there any reason that Bullets is written in singular and not plural form?
For me it is also interesting to see what other users and the UX team think about this already nice proposal.
(In reply to A (Andy) from comment #1)
> After taking a first look at it I would like to say that I like it already.
Glad you like it.
> Regarding point 2: This is very good, but where can I find this button in
> the mockup? You wrote it is at the bottom of each section. Or do you mean
> with this the already existing button at the top right of each section?
At the time i completed that mockup, the idea hadnt fully materialized, so its not shown in the mockup. :D
> Your link to the button screenshot looks at my computer unfortunately a
> little bit weird.
Its for those who may not have understood what the sidebar button is.
> Is the Page section folded as standard?
Yes it is folded by default currently in LO, but if this mockup is implemented, then the new page tab should also be implemented (bug 83830) to eliminate this section from the properties tab.
> In the section Lists can I there also change between Numbering and Bullets
> and what will open with the Graphics drop-down list? Is there any reason
> that Bullets is written in singular and not plural form?
Yes the drop down field is pulled as is from the bullets and numbering dialog box, so yes you would be able to select numberings and bullets.
> For me it is also interesting to see what other users and the UX team think
> about this already nice proposal.
You can read alot of the discussion between me and Mirek at < https://redmine.documentfoundation.org/boards/1/topics/69 >.
Created attachment 114216 [details]
Did some redesigning of the spacing and listing sections.
Spoke with Heiko and he stated that it would be preferred not to use split buttons found in the right mockup of attachment 114216 [details].
(In reply to Jay Philips from comment #4)
> Spoke with Heiko...
The planned guideline for sidebars will probably state that the main purpose is to tweak properties quickly (at least I will vote for this). Menu buttons, combo boxes, and overlay widgets (e.g. color) are not appropriate for this task.
Sidebars are for Benjamin-like user. So it must not be overwhelming with a lot of options. The full scope of features have to be available in dialogs.
We're replacing our use of the 'ux-advise' component with a keyword:
Component -> LibreOffice
Add Keyword: needsUXEval
This mockup has been discussed in the design team and is still used for decisions. Removing needsUX anyway as there is no need to discuss the idea.