Hi
Em 10-09-2011 15:44, Eike Rathke escreveu:
Hi Astron,
On Saturday, 2011-09-10 12:59:17 +0200, Astron wrote:
Yet, the problem for most people is that they have never extensively
worked with styles and might not understand intricacies like
inheritances.
I think much of the user's confusion can be avoided if the Stylist
didn't show the flat All Styles view initially, but the Hierarchical
view instead. This immediately gives a hint that styles depend on other
styles, even if the user has no idea of inheritance concepts.
indeed. +1
If the Organizer tab for derived styles then instead of the simple
"Contains" would say "Contains not in parent style" or "Items different
from parent style" or some such, things would be much clearer.
Eike
Interesting. Who has patience to read all the style spec's in the
organizer tab? I don't, for instance. And besides, the description is a
mess of specs, not categorized.
While we are at, how about a small window with the style redered on a
dummy text? There is a suitable real state in the dialog box.
Kind regards
--
Olivier Hallot
Founder, Steering Commitee Member - The Document Foundation
Voicing the enterprise needs
LibreOffice translation leader for Brazilian Portuguese
+55-21-8822-8812
Context
Re: [Libreoffice-ux-advise] to duplicate an existing style · Regina Henschel
Re: [Libreoffice-ux-advise] to duplicate an existing style · Cor Nouws
Re: [Libreoffice-ux-advise] to duplicate an existing style · Eike Rathke
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.