Thanks a lot for your response it
really give more insight into it, I just want to ask one more thing is
it like for each protocol we have all its attribute at one level like suppose
ethernet, so all ethernet attributes at one level than in next level all
IP attributes like that.
"Gilbert Ramirez"
<gram@xxxxxxxxxxxxxxx>
Sent by: wireshark-dev-bounces@xxxxxxxxxxxxx
06/10/2008 07:15 AM
|
Please respond to
Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx> |
|
|
To
| "Developer support list for Wireshark"
<wireshark-dev@xxxxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [Wireshark-dev] proto tree |
|
On Tue, Jun 10, 2008 at 7:10 AM, Guy Harris <guy@xxxxxxxxxxxx>
wrote:
>
>> what is the use of defining proto_tree and proto_item differently?
>
> I'm not sure what the rationale was for that. Gilbert?
>
That's for a very ancient historical reason. The original release of
Ethereal used GtkTree and GtkTreeItem objects (I don't remember the
exact name, but something like that). The decode info was written
directly to the GUI widgets. When I add the proto_tree layer on top of
the GUI widgets, I mimicked the widget classes "just in case".
Not a
very good reason, but historical.
--gilbert
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev
______________________________________________________________________
______________________________________________________________________
