Bug 69310 - (Plat) Filtering Capability in views
Summary: (Plat) Filtering Capability in views
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Hyades (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P1 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Terry Fountoulakis CLA
QA Contact:
URL:
Whiteboard:
Keywords: Documentation, PII, ui
: 64738 71812 73711 (view as bug list)
Depends on: 74483
Blocks: 74887 78322 87104 87105
  Show dependency tree
 
Reported: 2004-07-05 13:50 EDT by Eugene Chan CLA
Modified: 2012-02-15 13:44 EST (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Chan CLA 2004-07-05 13:50:25 EDT
prefix        d
name          rrunner 9604
reference     aix192599
abstract      F: Filtering Capability in views

    <Note by who (Wayne Ho), 2001/12/18 19:47:52, seq: 1 rel: 0  action: open>
Description:
Provide a consistent interface mechanism to provide filtering
capabilities within each view.

Resolution:
Each view should have a consistent method of accessing filtering
functionality.  It will be important to follow emerging Eclipse
UI Guidelines.  The likely path to follow will be a local
toolbar button on a view for filtering (or via the Views drop-down menu).  
When clicking on this Filter button, a Filter dialog will appear 
providing a number of options.  The dialog allows a number of 
filtering options.

We will need to consider the specific filters for each view
and this dialog may vary slightly from view to view.

    <Note by rduggan (Richard R.K. Duggan), 2001/12/20 18:20:36, seq: 2 rel: 0  
action: return>
Wayne,  we already have a working prototype of a 
UI filtering mechanism that is scheduled to go
in V5.  If you would like to see it please 
contact me.

    <Note by who (Wayne Ho), 2002/02/14 15:00:29, seq: 3 rel: 0  action: reopen>
I am reopening this Feature after having a number of design
discussions with Mike.  

A design document is available in the Problem Determination
UCD Database

Title: Filtering Designs
Server: D25DB01/25/A/IBM
Filename: function\ucd\problemDet.nsf

(on the Navigator click on the "General" tab and then look
in the "Library" under Design Documents"

Design Summary (note: see the Notes database for most recent design):
The basic premise of the design allows the user to
access filtering functionality via a Filter local toolbar
button in a view.  The filter button will also have an associated
drop-down menu allowing users to:

Edit the filter (opens an Edit Filter Dialog)
Quickly select the Current Filter Set (using a cascade menu to select)
Delete a Filter Set

The Edit Filter Dialog will allow users to pre-emptively
filter out items/objects such as classes, methods, and threads.

Filtering can also be done "directly" in the view, via selecting
and object in the view and using the context-menu to filter.  This
will automatically open the Edit Filter dialog and automatically
add the item into the filter.

    <Note by who (Wayne Ho), 2002/11/19 18:28:14, seq: 11 rel: 0  action: note>
Description:
* Allow users to filter information within the views 
* These are UI view filters (not to be confused with the collection filters)
* This allows users to drill-down in a view and find the problem
* It should be easy to quickly set filters and also clear filters to see all
  data in the model

Resolution:
A filter button should be made available in the toolbar for each view
that can be used as a "Filter Access Point".  Ideally, the toolbar
button would have a drop-down menu.

Single clicking on the toolbar button can open an Edit Filter dialog.
Single clicking on the drop-down will display the UI Filtering drop-down menu.

The drop-down menu can provide access to:
  Edit Filters...
  Select Filter Set -> [List of filter sets]

The Edit Filters dialog could use the same design as the collection filters
allowing users to create and remove filter sets, and to modify the current
filter set.

* It is important to ensure the designs easily distinguish between
  UI filters and collection filters
* Appropriate feedback is necessary to indicate UI filtering is enabled
  on a view (e.g., modifying the view's title).  "Heap (Filter: myFilterSet)"

Additional discussion is required to finalize the design.
Comment 1 Geary Ridings CLA 2004-10-05 17:22:42 EDT
I'd like to see this feature delivered soon. It would be very helpful for 
users to be able to filter views (especially complex graphic views) to remove 
data from consideration as analysis proceeds. To be able to persist that data 
so a user doesn't lose this work seems like an extremely useful capability.
It also seems useful to be able to set post data collection filters that are 
applicable across views, so that a filter for a method statisics view also 
applies to a call graph view, for example.
 Most useful would be a filter that applies to the view, but is saved relative 
to the current instrumentation results. So when I switch between different 
agents, my filtering should be different based on the analysis I did for that 
specific set of data. Is that the intent here?
 The filtering selection and application should obviously be extensible to 
allow new views to surface new filtering specifications in the filtering UI as 
well as applying them to the new views.
Comment 2 Harm Sluiman CLA 2004-11-09 21:44:50 EST
Targeted to 4.0 by the requirements team.
Please create a description document in CVS.
Comment 3 Curtis d'Entremont CLA 2004-11-12 12:04:34 EST
*** Bug 71812 has been marked as a duplicate of this bug. ***
Comment 4 Valentina Popescu CLA 2004-11-19 16:00:22 EST
*** Bug 74887 has been marked as a duplicate of this bug. ***
Comment 5 Valentina Popescu CLA 2005-01-10 16:02:15 EST
Updating feature target per 01/10 UI main committers meeting

The work is planned to be started on I1 and finished on I2
Comment 6 Valentina Popescu CLA 2005-01-13 22:21:29 EST
the advance filter dialog should extend to support showing range of records(eg. 
first 500, last 200, from record 5 to record 100) in both log view and log 
interactions view.
Comment 7 Valentina Popescu CLA 2005-01-13 22:21:39 EST
*** Bug 64738 has been marked as a duplicate of this bug. ***
Comment 8 Curtis d'Entremont CLA 2005-03-09 12:50:36 EST
*** Bug 73711 has been marked as a duplicate of this bug. ***
Comment 9 Curtis d'Entremont CLA 2005-03-15 18:34:07 EST
Setting correct version.
Comment 10 Eugene Chan CLA 2005-03-18 15:02:31 EST
MDV media-design request [1094] submitted
Comment 11 Valentina Popescu CLA 2005-03-25 20:33:10 EST
Icons will be handled by defect 89151
Comment 12 Eugene Chan CLA 2005-04-08 10:59:14 EDT
close feature