Bug 406153

Summary:	Label each widget in Brush Settings drop-down panel
Product:	[Applications] krita	Reporter:	Tyson Tan <tysontanx>
Component:	Usability	Assignee:	Krita Bugs <krita-bugs-null>
Status:	REPORTED ---
Severity:	wishlist	CC:	griffinvalley, scottpetrovic, tamtamy.tymona, wallie988
Priority:	NOR
Version First Reported In:	nightly build (please specify the git hash!)
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Tyson Tan 2019-04-02 15:14:25 UTC

Right now, Krita's gigantic Brush Settings drop-down panel (F5) are divided into 6 areas according to our user manual:

https://docs.krita.org/en/_images/Krita_4_0_Brush_Settings_Layout.svg

4 of the 6 areas are unlabeled. This is bad because:

1) It's difficult to provide support/instruction. When I was translating the user manual, I can see the author was clearly having difficulty pointing out where exactly is an option, especially when the option is located in Area D and E.
2) The UI's elements do not align.
3) The UI's elements do not have a clear visual pattern.

For a quick improvement, I think we can:

1) Area B: Rename "Presets" to "Presets List"
2) Area D: Insert "Engine Options" or "Options list" on top of the list.
3) Area E: Insert "Control Page" or "Settings Page" on top of the controls. 
4) Keep "List", "Page" in the titles, they are useful for context.
5) Maybe we can put "Info Bar" in Area A as well...

Comment 1 Tyson Tan 2019-04-02 15:17:27 UTC

Here are two excellent videos about UI/UX designs in professional software with gore panels:

Sibelius
https://www.youtube.com/watch?v=dKx1wnXClcI

MuseScore (It's Qt, and it looks like they are having similar issues!)
https://www.youtube.com/watch?v=4hZxo96x48A

Comment 2 wolthera 2019-04-08 14:02:56 UTC

I am going to set this to wishlist.

Comment 3 Scott Petrovic 2019-04-13 21:56:32 UTC

I think the brush editor is going to be changing quite a bit after the resource re-write gets done. There are ideas to condense this more...as well as make it detachable and more configurable.

Further UI work stopped on this because of the overlap that might happen with the resource rewrite branch. 

I agree this is probably one of the worst of areas of the UI that needs to be updated though. We also need to update the resource manager...which also is going to be impacted by the resource rewrite

Comment 4 Tiar 2020-04-07 15:39:36 UTC

The UI isn't affected by the resource rewrite much, so works can be continued, especially since now the resource rewrite branch is already merged, so all development happens on one branch and there is no issue of trouble while merging the code.