|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?
|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).
Maybe we can expand the context menu by replacing "Selected" with the field
name and value, if the selection is a field or protocol?
|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"; if no filter is available yet,
then the and/or options must be grayed out.
|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.
Regards,
Olivier
