Bug 148473 - Use field type for subtreeing in Navigator (note split of bug)
Summary: Use field type for subtreeing in Navigator (note split of bug)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Navigator
  Show dependency treegraph
 
Reported: 2022-04-08 20:37 UTC by Eyal Rozenberg
Modified: 2024-07-08 08:41 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
A typical Navigator view of some fields (39.37 KB, image/png)
2022-04-08 20:38 UTC, Eyal Rozenberg
Details
Screenshot (25.20 KB, image/png)
2022-07-08 07:27 UTC, Heiko Tietze
Details
A document with some cross-references (11.00 KB, application/vnd.oasis.opendocument.text)
2022-07-08 10:48 UTC, Eyal Rozenberg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eyal Rozenberg 2022-04-08 20:37:59 UTC
Currently, all (?) fields are presented in Navigator directly under the Fields root, with the field code/name and arguments serialized into a string. For example:

* Fields
|
+ - * cross-reference - __RefHeading__Toc415784771 - יב
+ - * cross-reference - __RefHeading__Toc4157846681 - 2

and so on; see attachment. This is not useful. In this bug, I suggest one way of improving this state of affairs: Use the field type to form subtrees. Fields are already effectively grouped by field type because of how the serialization works, so why not save the repetitions and just make the field types into subtrees? Even without touching anything else, that would already allow the Navigator to fit more field info in, and be easier on the eyes.
Comment 1 Eyal Rozenberg 2022-04-08 20:38:47 UTC
Created attachment 179418 [details]
A typical Navigator view of some fields
Comment 2 Dieter 2022-04-24 04:43:28 UTC
I think it is an advantage in documents with a lot of fields, but a disadvantage in documents with only five fields or less.

cc: Design-Team
cc: Jim Raykowski
for further input and decision
Comment 3 Eyal Rozenberg 2022-04-24 06:33:14 UTC
(In reply to Dieter from comment #2)
What about documents with only 5-or-less outlined paragraphs? Those are arranged in subtrees according to outline levels.
Comment 4 Heiko Tietze 2022-04-25 08:42:42 UTC
Wonder with what categories we end up. Number range, Date/Time, Page Number in case of my formatted dummy text (=> available at the extensions site).

But in principle IO agree with more hierarchy for large trees. Could have been also an option for the Foot/Endnote thingy.
Comment 5 Heiko Tietze 2022-07-08 07:27:26 UTC
Created attachment 181161 [details]
Screenshot

That's what I get with 

Version: 7.3.4.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 8; OS: Linux 5.18; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (en_US.UTF-8); UI: en-US
7.3.4-2
Calc: threaded

Looks good to me, please check again.
Comment 6 Eyal Rozenberg 2022-07-08 10:46:53 UTC
(In reply to Heiko Tietze from comment #5)
> Looks good to me, please check again.

Your screenshot doesn't affect this bug that much. It still makes sense to have a subtree for cross-references, and within that for different types of references etc. - and the same for other kinds of fields. In your example there are few fields from every kind.
Comment 7 Eyal Rozenberg 2022-07-08 10:48:48 UTC
Created attachment 181172 [details]
A document with some cross-references
Comment 8 Heiko Tietze 2022-07-08 11:09:28 UTC
(In reply to Eyal Rozenberg from comment #7)
> Created attachment 181172 [details]
> A document with some cross-references

...showing the category and object names. The _RefHeading_* labels show proper names now. WFM?
Comment 9 Eyal Rozenberg 2022-07-08 11:54:40 UTC
(In reply to Heiko Tietze from comment #8)
> (In reply to Eyal Rozenberg from comment #7)
> > Created attachment 181172 [details]
> > A document with some cross-references
> 
> ...showing the category and object names. The _RefHeading_* labels show
> proper names now. WFM?

Well, though the problem is less significant now, it would still be useful to create a subtree per field category, and the items in the subtree will just have the names, not also the category.
Comment 10 Eyal Rozenberg 2022-07-08 11:55:23 UTC
(In reply to Heiko Tietze from comment #8)
> (In reply to Eyal Rozenberg from comment #7)
> > Created attachment 181172 [details]
> > A document with some cross-references
> 
> ...showing the category and object names. The _RefHeading_* labels show
> proper names now. WFM?

Oh, wait, actually, no. I still see the RefHeadings. So, let's split that off into a different bug.
Comment 11 Heiko Tietze 2022-07-08 12:05:50 UTC
Okay, let's use sub-categories for fields. 

About the second issue, I don't get the _refheading_. Good for another ticket if you have clear STR.
Comment 12 Eyal Rozenberg 2022-07-08 12:13:52 UTC
(In reply to Heiko Tietze from comment #11)
> About the second issue, I don't get the _refheading_. Good for another
> ticket if you have clear STR.

Done, bug 149916.
Comment 13 QA Administrators 2024-07-08 03:16:31 UTC Comment hidden (obsolete)
Comment 14 Eyal Rozenberg 2024-07-08 08:41:07 UTC
It's still the case that the field type gets concatenated to the specific field name for the Navigator entry, rather than us getting a subtree.

Version: 24.2.4.2 (X86_64) / LibreOffice Community
Build ID: 51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2
CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3
Locale: en-IL (en_IL); UI: en-US