Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hey.

Since I'm running out of time, just a short reply :-)
I'm going to start with: that's still an alot of things to ponder...
Thank you for all this input, also on the buttons proposal -- I didn't
even think of most of these scenarios (although they should have been
fairly obvious). I'll try to address at least some of this in tomorrow
or Tuesday in the wiki. By the way, I'm really preferring version 1 of
these.

Oh, I really liked your sketches! Here is something I've wrote about
last year:
http://uxopenofficeorg.blogspot.com/2010/05/picture-is-worth-thousand-words.html
Hm, I am a bit wary of posting my handwriting on a wiki for all to
see, because, while I like it, it is not always too clear. And also
the Inkscape mock-up was done in the same spirit (at least I tried).

Oh, sorry, I haven't been clear enough here ... we have a great
documentation team, but nevertheless, such changes will have affect on:
internal/wiki help, external documentation, training material ... in
almost 100 languages ... and also the training effort (in companies).
And that's the real issue - and that's what requires to be very careful
about change affecting many users.
Ugh. When you have more time later, would you mind explaining how
careful we have to be? I'm a bit unsure, for instance: are wording
changes easy to take care of (just search and replace some words in
all documents)? What is a careful interaction change?

* this mock-up doesn't use "AutoCorrect", but rather something that I
Ouch. That should of course mean "AutoUpdate"...
hope is more digestable: "automatically update this style when
formatting is changed directly" (I suppose the wording could still be
improved)

True, already improved ... :-) But, at some point we have to keep two
things in mind (don't worry, let's first discuss the behavioral and
structural changes):
     * there is an OOo styleguide how UI / help texts should be written
       (to be consistent throughout LibreOffice)
I tried googling for it, is this the right document/version?
http://specs.openoffice.org/collaterals/guides/text-style-guide.html

     * we are heavily affected by the size of the dialogs, since
       English is a rather "compact" language, but the dialog size has
       to reserve space for other languages (rule of thumb: English
       +40...60% space) --> we really need a layout manager, grrr
I see there's something making you rather less happy^^. From your
experience, is it feasible to leave some blank space under that line
so that text can flow more freely or would that look unprofessional?
In this case, I'm unsure, how to, after leaving out the "that," the
idea can be put in a more compact way -- unless one wants an Auto-ism
as before.


* the field "Contains" is replaced by a more ordered and professional
looking list, from which single items can be selected and removed
Using the list alone is a great improvement already :-)
I'd hoped that.

How about moving the "Inherits from" above the "Style defines", then it
might be clearer how "inheritance" works?.
Not sure. Since really, it is a relation to another style. I don't
think these should be important enough to warrant putting them above
the actual definition of the style. And also, I tried to keep it
somehow in order in the Refererences grouping (General type of class,
Base class, Followed-by class -- although I just see that this
hierarchy isn't really one at all). But I'm fairly sure that changing
that text again to "based upon" will not only translate better but
also communicate more clearly.
I also think that "[this] style defines[:]" is not very good wording,
but I left it because the current "contains" or "definitions" seemed
worse.

Great work, really! I'm sorry that my time is so limited at the moment,
so my support is rather limited ... so please feel free to point out
things you might need help with / comments / moral support ;-)
Thank you. You've brought up many important things here already.

Regards, Astron.

-- 
Unsubscribe instructions: E-mail to design+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/design/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.