Bug 148464 - Ability to pick-and-choose where to search
Summary: Ability to pick-and-choose where to search
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Find&Replace-Dialog
  Show dependency treegraph
 
Reported: 2022-04-08 11:36 UTC by Eyal Rozenberg
Modified: 2022-04-26 07:44 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eyal Rozenberg 2022-04-08 11:36:15 UTC
There are different categories of content in a document; and while one could nitpick about exactly what those are, we can look to the Navigator for a list. We have (in no particular order): 

1. The main body of the document
2. Footnotes
3. Endnotes
4. Headings / paragraphs with an outline level
5. Tables
6. Captions
7. Bookmarks
8. Hyperlinks
(9. Cross-references)
(10. Indices / ToCs )

... and note that not all of these are disjoint, e.g. the main body contains many of the other categories, heading paragraphs often contain bookmarks etc.

Anyway, when searching for content, I want to be able to indicate, for each of these categories except perhaps the last two, whether I want it to be searched or not (and so that content is searched if it falls in at least one category I've requested, so that the overlap between categories is not painful).

At the very least I would like to be able to choose just one of these categories, which would not be sufficient but would save me from doing a huge amount of work sifting through results.

The specific case of comments is the subject of bug 148463; it's a bit different since there's already some UI regarding whether or not to search comments.
Comment 1 Heiko Tietze 2022-04-11 10:38:34 UTC Comment hidden (obsolete)
Comment 2 Heiko Tietze 2022-04-11 10:40:03 UTC Comment hidden (obsolete)
Comment 3 Eyal Rozenberg 2022-04-11 11:28:24 UTC
(In reply to Heiko Tietze from comment #1)
> Is this about the F&R dialog/workflow or the to be introduced Navigator
> search?

Actually, not just the F&R dialog but perhaps also the find bar.
Comment 4 Eyal Rozenberg 2022-04-25 18:13:55 UTC
(In reply to Heiko Tietze from bug #96474 comment #10)
> The topic was on the agenda of the design meeting.
> 
> Solution a) is to list all entities similar to attributes and check it by
> default. The idea in comment 3 is not flexible, hard to understand and takes
> a lot of space.
> Solution b) would be to know where the search was started from and allow to
> "[ ] Search only in %1".
> Solution c) is to start the search command with a parameter like
> .uno:Search?where="comment" and allow to restrict the search to this entity
> only
> 
> Solutions b) and c) clutter less, a) is more flexible (but requires a check
> all/none option).

I'll rephrase, since the minutes mis-capture my opinion as it evolved over the course of the meeting..

(a) (b) and (c) are for me all parts of the same solution:

* A sub-dialog of the F&R dialog will list all _kinds_ of entities, just like we currently have for Attributes. The entries could be something like: Body, footnotes, endnotes, comments, footers, headers, headings etc. etc.
* The initial selection on this dialog will depend on how or from where you got into the F&R dialog. For example, if the comment context menu had an item called "search comments", it would bring up F&R with only comments checked; but the main menu item would not do that. One can bike-shed what the default selection should be, and whether using the same menu item from different places should affect the default.
* The initial selection can be overriden by a parameter of the UNO command, which would be a list of checked/selected items. So, the way a "search comments" would be implemented is the F&R dialog command, with a setting of the initial selection parameter to only have comments.
Comment 5 Heiko Tietze 2022-04-26 07:44:50 UTC
Removing UX keyword to implement as suggested.