Ethereal-dev: [Ethereal-dev] Re: Ethereal-dev Digest, Vol 8, Issue 22

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: Tue, 09 Dec 2003 22:55:23 +0100

Date: Tue, 9 Dec 2003 10:40:08 -0800 (PST)
From: Richard Sharpe <rsharpe@xxxxxxxxxxxxxxxxx>
Subject: Re: [Ethereal-dev] What is "File->Save Highlighted" menu item
	for?
To: ethereal-dev@xxxxxxxxxxxx
Message-ID: <Pine.LNX.4.44.0312091038010.4430-100000@durable>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 8 Dec 2003, Guy Harris wrote:

On Tue, Dec 09, 2003 at 07:43:07AM +0100, Ulf Lamping wrote:
Richard Sharpe wrote:
OK, the current label does not indicate that only the highlighted packet data is saved ... Perhaps we want Highlighted Packet Data or something like that.

I would tend to call it "Selected", not "Highlighted".

Or is there a reason to use the term "Highlighted" that I just don't see?
What's written is the field you've currently selected in the protocol
tree pane.  If, for example, you happen to select some text in the hex
pane, that doesn't affect what gets written (for one thing, you can
select stuff that's not on byte boundaries, or that crosses between the
hex dump and ASCII dump portion).

I wanted to avoid confusion with other things that we do, like packet marking etc.

Since this facility saves the bytes associated with a select field or highlighted field or a subtree or item, perhaps it is better if we use the label

  Highlighted field

or
  Selected field

?

I first missunderstood, that this would save some selected bytes in the byte view, so "Highlighted" would be *maybe* a suitable name for it in this case.

But as I understand now, this will save all the bytes of a tree (or partial tree), in this case I would strongly suggest to use the term "Selected" here.

In conclusion to all this, "File->Export->Selected Protocol Field" seems to be a suitable name here for me.

This doesn't has to be a name valid until doomsday. If we get more export functions later, it could become clearer to get an even more suitable name for this.

Regards, ULFL