Bug 135422 - Show API property names as tooltips in Styles Inspector
Summary: Show API property names as tooltips in Styles Inspector
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Style-Inspector
  Show dependency treegraph
 
Reported: 2020-08-03 19:31 UTC by Mike Kaganski
Modified: 2022-08-05 03:32 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2020-08-03 19:31:57 UTC
 f39f37326ac787e88a0782915afac91cf418a539 makes displayed property names "human-readable" and translatable. But internal API names of the properties may also be very helpful for Styles Inspector users: e.g., those who write macros, and may want to see the names of properties in a sample data.

Styles Inspector should provide the API names either in a tooltip, or in a third column (less desirable IMO).
Comment 1 Heiko Tietze 2020-08-04 06:19:08 UTC
It's a quite technical information and I rather tend to disagree with this enhancement than adding another column. Tooltips don't hurt too much OTOH.
Comment 2 Mike Kaganski 2020-08-04 07:50:42 UTC
Yes, I also like tooltips better; see e.g. how they are implemented in Customize dialog (Menus tab, Available Commands box).

Additionally, the tooltips for SI could also include ODF element/attribute name (to further help people understand how API properties relate to open file format structure), like this two-lined tooltio for some entry like "Property Foo":

> API name: PropFoo
> ODF element: propBar (or ODF attribute: attrBaz)
Comment 3 QA Administrators 2022-08-05 03:32:03 UTC
Dear Mike Kaganski,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug