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


Hi all,

@Christoph:
Well, that was the case some versions ago - then the current behavior
(save icon is always active) has been introduced. Reason: There has been
customer feedback targeted at the Sun OOo UX Team that people wish to
press that button at any time - just to be sure that the document is
really saved. So here its not about real logic, but about people to feel
"safe".

If that was the case, then it would have been a better idea to focus
on the following things:
* get document backup/restoration reliable enough for everyone
(something like backup-as-you-type maybe)
* make sure, Ooo doesn't crash (and if it crashes, that it doesn't
take all opened documents with it – for instance, similar to how
Chrome separates tabs)

(Yes, that's an arrogant statement coming from a non-developer. I know that.)


Almost the same is true
for the current status bar indicator - but of course it's just there
because of the cool TDF symbolism ;-)

That's a terrible reason to introduce new UI. The world most of us
live in is cluttered with branding and ads, so to me it's not a good
idea to add to this beyond what we actually need to establish a brand.
Long-term, I would love if we could reduce the amount of logos to the
ones contained in the about box and the one in the titlebar. (Splash
screen should go completely at some point and the logo in the start
centre seems unnecessary to me.)
Maybe I'm an extremist here.


So, finally, if there is a need to further cleanup the status bar, then
I'd propose to go with "(unsaved)" instead of the asterisk for the title
bar. Example for unsaved changes:
       Strategy Document (unsaved) - LibreOffice Writer

I've seen other software go for "(modified)" which is a more positive
word, I think. So, that would be my preferred solution.

To shorten the text in the titlebar again, we could follow the Gnome 2
guidelines and remove the "LibreOffice Writer/Calc/..." part of the
titlebar.


@Jean-Francois:
A document is either changed and needs saving or is not and... doesn't.
Conversely, if changing a property needs saving, then the document *is*
changed.

Maybe it's not quite that simple. There are certain settings (zoom
level, for one) that depend so much on the specific computer (screen,
in this case) that it doesn't make a lot of sense to even save this
information within the file. It would make far more sense to save that
in the LibreOffice configuration itself. This way, you can just save
those settings when the window is closed.
For other settings like caret position within the document, that
approach might not be applicable, however, given my example, if you
put your caret at a different position within a document, then this is
usually done to edit it, thus producing a new saveable state.
Since I am not sure what else is saved within the document, I won't go
on here... I hope you see the point.

In any case, I don't have so much of an opinion about whether to
actually enable the save icon at all times ... both options are fine
with me.
I would, however, like the statusbar indicator to be gone.

Astron.

-- 
Unsubscribe instructions: E-mail to design+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/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.