[Libreoffice-ux-advise] [Bug 143249] UI: Improve handling of configuring table borders in table properties dialog (to make it work for multiple workflows)

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=143249

--- Comment #26 from Mike Kaganski <mikekaganski at hotmail.com> ---
When we discussed the mockup from comment 15 on the call, in the beginning, we
indeed discussed some workflow change. But in the end, our discussion came to
this mockup, which intended to *not* change workflows, but instead to make the
actions more obvious and accessible.

Current (and proposed with the mockup) workflow focuses on one central idea: at
any point in time, all *selected* borders have the same set of properties
applied. This is not only difficult to change, but also is undesirable to
change. This also implies one important property: *both* orders of operations:
"select then configure" and "configure then select" result in the same set of
properties applied to the selection.

The border settings definition is necessarily complex, because we try to fake
"simple property  setter" for something that indeed is complex: multiple
separate objects (up to 8 individual borders, with several elementary
properties - color, width, style - for each). An alternative would be having
too many individual simple controls - and that would be even worse.

The proposal has the following advantages:
1. Introduce individual buttons to *select* individual borders (previously,
that was only possible by clicking on parts of the preview). This allows to
have *accessibility*, as well as UX improvement by hinting people who don't
guess where and how to click on the preview.
2. Moving presets to an own panel, potentially allowing to define own presets.

The problems with the mockup:
1. The "visible" should be kind of radio button (or a drop-down), with these
options: none/visible/unchanged (to match current options). Visible means the
controls below enabled; other two modes mean controls below disabled.

-- 
You are receiving this mail because:
You are on the CC list for the bug.