Bug 305829 - [Webapp] Support switching search results between "flat" and "hierarchical" view
Summary: [Webapp] Support switching search results between "flat" and "hierarchical" view
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: platform-ua-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-15 06:16 EDT by Martin Oberhuber CLA
Modified: 2019-09-06 16:18 EDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2010-03-15 06:16:29 EDT 
+++ This bug was initially created as a clone of Bug #303105 +++

As a user who just searched the help system, I am overwhelmed by a flat list of too many match results. I would like to switch the presentation of search results between a "flat" and "hierarchical" view like the Eclipse Platform search supports it, such that I can understand the categories and contexts in which my search results are found.

Instead of showing the entire TOC hierarchy, a "group by book" functionality might also be helpful.
Comment 1 Martin Oberhuber CLA 2010-03-15 06:17:34 EDT 
Addon: Understanding the hierarchies in which the search results are found may also help enabling a proper filter or search scope for TOC and search results, such that the next search produces better results.
Comment 2 Martin Oberhuber CLA 2010-03-15 07:34:45 EDT 
Note that in the IDE help view, there is already a related button ("show result categories"), but the categories would need to be collapsable to provide real value.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:18:14 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.