[Libreoffice-ux-advise] [Bug 151507] Themed color palette

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Thu Mar 30 19:03:51 UTC 2023


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

--- Comment #8 from Regina Henschel <rb.henschel at t-online.de> ---
Created attachment 186332
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186332&action=edit
Solid fill and gradient fill

Theme colors (MS Office "schemeClr") are different from palettes because the
set of scheme colors is stored in the file and bound to the master page. As
Writer has only one master page it can only have one set of scheme colors.
Impress/Draw can have several master pages and thus several sets of scheme
colors.

If you want to change a theme, that means effectively a change of the master
page. So I agree with V Stuart Foote that changing or editing the set of scheme
colors should not be in the area dialog but could be located in the master page
dialog in Impress. In Writer it cannot be inside the page style dialog, because
there is only one set of scheme colors. [Perhaps a new dialog with all document
wide settings in Writer?]

For selecting a scheme color, I prefer to have it separated from the palettes.
There could be a dedicated area for it, see my attachment.

Lighten/darken can be a new control, consisting of a set of buttons with
stepped examples and a field for numerically determine the value. MS Office
allows light and darken not only for scheme colors but for all colors.
Therefore I would allow lighten/darken for palette colors too. See my
attachment.

MS Office has no fixed steps of lighten/darken but depends the steps on the
brightness of the base color. So should we do (bug 153361). It is useless to
make a light background color 4 steps lighter, or a dark text color even
darker.

The previews of the selected colors would then need to be split in showing the
base color and the selected lighten/darken variant. That is not included in my
attachment.

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


More information about the Libreoffice-ux-advise mailing list