Ethereal-dev: RE: [Ethereal-dev] [RFC] Match and Prepare context menu itemnames

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Ulf Lamping" <ulf.lamping@xxxxxx>
Date: Wed, 05 May 2004 14:46:49 +0200
Ethereal development <ethereal-dev@xxxxxxxxxxxx> schrieb am 05.05.04 13:43:18:
> 
> |From: Ulf Lamping
> |
> |
> |Hi List!
> |
> |I'm thinking about renaming these entries.
> |
> |Currently, we have the context menu items named "Match" and 
> |"Prepare". This is a bit short and not easy to understand.
> |
> |I would tend to rename it:
> |
> |Match   -> Apply as Filter
> |Prepare -> Prepare a Filter
> |
> |Explanation:
> |The term "Apply" is already used in the GUI, and better 
> |explains what will be done (compared to "Match").
> 
> Match does 2 things:
> A. Edit the display filter
> B. Apply the modified display filter
> 
> Prepare does 1 thing:
> A. Edit the display filter
> 
> Maybe we can choose between "Edit the filter" and "Edit and then run the
> filter" as options?

"run the filter"???

Sorry, I don't get the point.
> 
> |Question: What's better: "Apply as Filter" or "Apply as 
> |Display Filter"?
> |
> |
> |Selected         -> Selected
> |Not Selected     -> Not Selected
> |And Selected     -> ... and Selected
> |Or Selected      -> ... or Selected
> |And Not Selected -> ... and not Selected
> |Or Not Selected  -> ... or not Selected
> 
> I'd really want to have the "is present" test to be available too (as 1st
> item).

Agreed, "is present" would be nice (but not as the 1st element, because Selected is the most commonly used item, at least for me).

> 
> Maybe we can expand the context menu by replacing "Selected" with the field
> name and value, if the selection is a field or protocol?

I'm currently looking exactly how to do this (didn't found an easy way until now), as this would "boost" intuitivity IMHO.

> 
> |Explanation:
> |I want to distinguish "visually" between the subitems that 
> |replaces the filter and the ones that will append to the 
> |existing string in the filter text entry.
> |Question: Any better term for ...?
> 
> You may replace "..." with "Current filter"; 

That's a bit too long, I think.

> if no filter is available yet,
> then the and/or options must be grayed out.

Yes, that's related to fill in the currently selected "thing" into the menuitems label (currently I just don't know how, but looking at it).

> 
> |I've done some experiments in my personal source tree, and 
> |it's looking much "easier" this way.
> 
> I also believe we need to add clarity in this item.
> 

Yes!

Regards, ULFL

_____________________________________________________________________
Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Netsky.A-P!
Kostenfrei fuer alle FreeMail Nutzer. http://f.web.de/?mc=021157