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


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

Heiko Tietze <heiko.tietze@documentfoundation.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needsUXEval
                 CC|heiko.tietze@documentfounda |libreoffice-ux-advise@lists
                   |tion.org                    |.freedesktop.org

--- Comment #9 from Heiko Tietze <heiko.tietze@documentfoundation.org> ---
(In reply to Julien Nabet from comment #6)
Xisco/Heiko: what options should we add from UI point of view?

I don't see much need for formatting. The point of sheet protection is to share
some ready made content. Printing yes/no, Recalculation and updating data
sources comes in my mind. All with PDF export in mind where printing, changing,
and access is optional. And to complete this it would be nice to have parts of
the document readonly or also hidden too, let's say the calculation method, but
allow to insert variables. Think it's possible out of the box.

The summary reads more like granting access to a range of users (eg. admins vs.
ordinary user, or *@foo.com +rw, *@bar.com +r-w). Sounds too complicated to me.

Nice topic for the UX people anyway, will add this to the weekly meeting.

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

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.