Unable to Protect/Unprotect cells in Libreoffice 5

users
#21

jorge-2 wrote

...

   How we can help with this ?

   We, the users can make one example to each topic of the menu of
LibreOffice can do. Then when coming new version before out we can probe
each example during one week and make a report to programers. With this
reports, just following the menu, they can fix the bugs that apear before
freeing the new version.

   The other way is to make a macro to probe each topic of the menu to do
it automatically.

It is already there.

LibreOffice "Regression Testing," both automated and manual, is continual
and ongoing:

https://wiki.documentfoundation.org/QA/Testing/Regression_Tests

Individuals, please note that the LibreOffice project runs a MozTrap based
test suite for performing exactly this manual testing--with guided test
cases--but it is woefully underutilized by the broader user community. If
you are interested, check it out:

https://wiki.documentfoundation.org/MozTrap/User_Guide
http://manual-test.libreoffice.org/results/runs/?

The learning curve is a little steep for folks to get registered and get a
test case open, but is worth the effort as the results ARE reviewed and
integrated into the QA process. The Engineering Steering Committee reviews
results bi-weekly.

Thanks for this information!!! I wasn't aware of this until now. This
is something I would definitely be interested in participating in!

Thanks!

Peace...

"The other" Tom

#22

Hi V Stuart Foote and all:

  Thank you very much for this information ... I haven't known about it.
I will start to read your links to learn more about this project (LO)
and to try to understand too to give then if I can my little
contribution.

Regards,

Jorge Rodríguez

#23

Thank (all of) You for Your commitment.

Once you'll get used to that (let's say within 6 months), please consider
applying for membership as well.

http://www.documentfoundation.org/foundation/application-for-tdf-community-membership/

#24

Hi Gabriele:

  Thank you very much

Regards,

Jorge Rodríguez

#25

Done: bug 93837

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

#26

Hi

I created an extension that adds a submenu, Cell Protection, to the context
menu of tables. Feel free to give feedback, and I will try to publish the
extension to the LibreOffice Extension Center.

Note that at the moment the extension is in English only.

For the time being, you can download the extension from:
https://www.dropbox.com/s/3e3ok1kxyrshay8/CellProtectContextMenu.oxt?dl=1

/Niklas

#27

Awesome, thanks Niklas!

I probably won't be able to try it until Tuesday, but will do so as soon
as I can and let you know how it goes.

Thanks again!

On that note...

I wonder - would it be possible to create a more generic (and I'm sure
more complicated) extension that allows you to create new sub-menu
content entries like this?

Or, maybe, just one that allows you to add one of the main menus (ie, in
this case, 'Table') to the context menu?

Anyway, just thinking how to make it more useful to others...

Thanks again!

#28

Hi

...
I wonder - would it be possible to create a more generic (and I'm sure
more complicated) extension that allows you to create new sub-menu
content entries like this?

Or, maybe, just one that allows you to add one of the main menus (ie, in
this case, 'Table') to the context menu?

Anyway, just thinking how to make it more useful to others...

Well, the short answer is that sure it is possible, but it is quite an undertaking to do it.
It would require time that I simply don't have at the moment. However I'll probably
look into doing it, or at least a simplified version of it from time to time. :wink:
One of the harder part would be to create a simple and intuitive dialog for the
feature.

Might be good to note that it is definitely easier to add context menu entries if
I only now what to add and where.

/Niklas

#29

Hi Niklas,

Just fyi, the extensions works great!

One thing... I do use the Quickstarter, and I tried the extension right
after installing it - without restarting the Quickstarter - and
Libreoffice went into some kind of strange loop right after I
right-clicked on a cell in a new table inserted into a new/unsaved
writer doc.

I had to kill Libreoffice (kill all of the soffice.bin process), and
after that, it is now working great.

Thanks very much!!

#30

Oh...

Any chance you can add the extension to the bug as a potential
workaround for others?

Or, I'd be happy to do it if you're ok with it.

Thanks again!

#31

"Unprotect cells" has been added after "Protect Cells" on the Table menu for
the 5.0.2 rc1 build.

The Writer Table context menu for "Cells" has been trimmed of bloat as
indicated.

Niklas' Python UNO extension inserts a *Cell Protection* section with
*Protect* (.uno:Protect) and *Unprotect* (.uno:UnsetCellsReadOnly) entries
on the Writer Table Cell context menu, and I've uploaded a copy to the
tdf#93837 <https://bugs.documentfoundation.org/show_bug.cgi?id=93837> --"
Allow customization of the Context Menus" enhancement request for any that
care to restore it to the context menu.

#32

One mans 'bloat' is another mans gravy.

Please remember your classifying those context menu selections as
'bloat' is pure and mere opinion, nothing more.

I repeat...

This should NEVER have happened without first providing users a way to
customize these menus.

#33

Tanstaafl wrote

One mans 'bloat' is another mans gravy.

Please remember your classifying those context menu selections as
'bloat' is pure and mere opinion, nothing more.

I repeat...

This should NEVER have happened without first providing users a way to
customize these menus.

Hmm Charles, that seems rather like an opinion to me... especially as
Niklas demonstrates you can customize them--after a fashion. Though doing it
with extensions very quickly gets messy.

And as noted, providing customization of the context menu structures
requires substantial code refactoring that is not likely to happen anytime
soon--so saying changes should NEVER have happened is pure tripe. Just
because you personally were not involved does not make the Design and UX
decision any less valid.

Design, development, QA is an ongoing volunteer effort, predominately merit
based. If you would like to have a voice in that aspect of the project then
you have to volunteer some effort. And yes, I know you've been active on
the User ML for years and contribute often in that sense--but if you would
like more say, step-up.

On that note, have you taken the time to download and install (in parallel
is fine) current master? As noted, there is a lot more change to menu,
toolbar and context menu behavior coming for the 5.1 release. These are
changes that have been committed into master since the 5.0 branch on 20 May.

Sorry, but the most effective time to comment is as changes are being
made--and that is on master branch. With weekly imput from Design and UX
advise collaborators and the QA and Dev community that follow along and use
these developmental builds. The time can not be when releases have been
finalized, spun and delivered--objections or "contributions" made then are
much less effective and of limited impact.

V Stuart Foote
QA, a11y advocacy, Desgn & UX advise, code contributor and hey a TDF member