Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[hyades-dev] Hyades UI meeting notes (Nov. 10, 2004)


Meeting notes from this week's Hyades UI meeting:

Agenda:

Continue the filtering discussion (part 4). Use cases were written after the previous meeting to clearly define what was talked about during the meeting. We will review these to ensure a clear understanding. Some things that come to mind that we may need to talk about:

1. Multiple post-filters enabled at the same time or not? If so, include an item in the drop down to disable all?

2. In-line editing or edit dialog for criteria?

3. Complexity of having to give your filters a name.

4. Associate filters with agents, agent types, or views?

5. Only show the last 10 filters in the drop down list?

6. How to make it clear to the user which filter(s) are currently enabled in the view.


Attendees
:

Carl Wicklow
Cheryl Adams
Curtis d'Entremont
Eugene Chan
Geary Ridings
Glenn Weidner
Marius Slavescu
Martin Boag
Terry Fountoulakis
Valentina Birsan
Wayne Ho

Time
:


Wednesday, Nov. 3, 12:00pm (noon) EST.

Notes
:


Here are the conclusions we reached:

1. A single filter enabled at a time.
2. Each filter is given a name by the user.
3. Filters are shared among agent types (i.e. profiling, logging, statistical). Different types of profiling agents still share the same filters.
4. Last n filters will be shown in drop down list (somewhere in the range of 5-10). List is sorted by time last used.. most recently used showing up at the top. Least recently used filters are the ones dropped when the list is full.
5. When setting a filter on one view, it automatically applies to other similar views (those that apply on the same agent type). This seemed to be the preferred approach over making it view-based. Although there are arguments and use cases for both ways. We can try this approach first, and see how it goes. In the future we can add a preference and possibly change the default to make it view based if we find that this approach is better.
6. If trying to apply a shared filter that doesn't fully apply to a view, it does nothing. For example, if you create a method filter in the execution statistics view then try to apply that filter on the memory statistics view (where there are no methods), it will have no effect.
7. This filter redesign work is targetted to Hyades 4.0.

Things still not decided:

1. How to show which filter is enabled on the view. The proposals were:
        a) add filter name to view title
        b) add filter name somewhere in the view
        c) use a different icon for the filter button to show whether or not the view is filtered
        d) make the filter button a toggle button to turn on/off filtering
        e) state how many things are filtered out (e.g. showing 100 of 150 elements).

2. How to turn off filters. The proposals were:
        a) a default filter set "No filters" that's always there in the list
        b) reselect the same filter in the list which causes it to toggle off
        c) make the filter button a toggle button

Thanks,
Curtis d'Entremont
Problem Determination Tools
IBM Toronto Lab

Phone: (905) 413-5754
E-Mail: curtispd@xxxxxxxxxx


Back to the top