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


Hi mirek,


mirek2 wrote
The original idea was to not have a static size for the overlay, but
rather
have its size detemined by its contents

But it was static. Only half the space was used. And I have many templates
and it was unpractical with this tiny place.



mirek2 wrote
, in the same way it works on
Android (and as was designed for our Android port), and similar also to
iOS/new Mac OS X behavior.

Why such priority for Android? Be consistent with Android, ok, but not being
consistent with the desktop is a mistake. LO is mostly a application to work
on desktop. So to being consistent on PC is important too. This is still a
productive application.



mirek2 wrote
It was imagined that there would only be one level of hierarchy (as is
standard on Android and iOS), as it makes browsing templates much simpler
and will be necessary if/when there is sync functionality between Android
and desktop LibreOffice.

Why limitating other users with such restrictions?
Other users may have more than one level.



mirek2 wrote
Thus, a path bar would be largely unnecessary

A path bar works for everyone.

I think we should not forget that the software  is used mostly on PC.

Regards,
Olivier



--
View this message in context: 
http://nabble.documentfoundation.org/Template-manager-feedback-tp4024102p4024237.html
Sent from the UX-Advise mailing list archive at Nabble.com.

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.