Ethereal-dev: Re: [Ethereal-dev] 0.10.2 release

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: Sun, 22 Feb 2004 21:28:17 +0100
Richard Sharpe wrote:

On Sun, 22 Feb 2004, Ulf Lamping wrote:

Hmmm, I just checked in some major rework of the menu structure of Analyze/Statistics:

Sorted by ISO-layer then by alphabetical order.

Well, it does not look very nice at the moment. It creates one hugh long menu.

Can we make it a submenu, and then sorted the way it currently is.
I was thinking of this topic too.

Simply putting the stuff into a submenu will keep things in a very deep menu structure, which should be avoided IMHO. I tend to make a complete new toplevel menu item, maybe "Layers" / "Details" or such, but I'm really not sure about that.

So the toplevel menu could be one of:

File Edit View Capture Analyze Layers Help
File Edit View Capture Analyze Details Help
File Edit View Capture Analyze Transport Application Help
File Edit View Capture Analyze Link Network Transport Application Help

Also, I wonder if the old scheme did not make more sense?
Are you really sure?
All the people I was asking about the Statistics, they tell me it's a very confusing menu structure,
so I started to think about a way to make it better.
If it's really better now is a different question.

For example, what is watch protocol for? It seems it was so you could get stats about that protocol during a live capture.
Well, please don't blame me on the names that the functions already had ;-)
I made only minor changes to this things.
Of course, it would be good to have a better name here, any suggestions welcome :-)
Suggestion: I would prefer (Statistics) instead of (Watch Protocol)

BTW: This shows that the previous structure wasn't very good, as you didn't saw this things before ;-)

That being the case, wont this make life more difficult for people?
For which people? For the one's already knowing the old structure, or for the one's newly starting to use Ethereal?

For me personally, when working with Ethereal captures, I usually have a specific protocol in mind,
and now looking for some ways to get more information from it.

The previous structure was the other way round, you had to have a function in mind,
and then look after the protocols implemented this function.



I just only wanted to help ....

Regards, ULFL