Ethereal-dev: Re: [Ethereal-dev] port to OS X

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

From: Guy Harris <guy@xxxxxxxxxx>
Date: Tue, 23 Apr 2002 13:02:16 -0700
On Tue, Apr 23, 2002 at 09:49:16PM +0200, Michael Tuexen wrote:
> I think the ethereal code is coupled with the glib stuff.

GLib does not depend on GTK+, so you could use GLib with other GUIs. 
(GTK+ depends on GLib, however.)  Eliminating the GLib stuff isn't
necessary to make Ethereal work with other GUIs.

> The GUI stuff is only available the ethereal code, but not in the
> tethereal stuff.

Yes - dissectors must *NOT* contain any GUI code, so that they can work
with Tethereal as well as Ethereal; this would also allow them to work
with GUIs other than GTK+.

Similarly, the stuff in the "epan" and "wiretap" directories also
contains no GUI code.

Some of the stuff in the top-level directory is support code for
dissectors:

	afn.c
	asn1.c
	in_cksum.c
	ipproto.c
	ptvcursor.c
	reassemble.c
	xdlc.c
	xmlstub.c

and some stuff in "util.c".  That stuff also contains no GUI code.

"prefs.c" is used by dissectors as well as by the core of Ethereal and
Tethereal; it contains no GUI code.  Some other files:

	capture_stop_conditions.c
	column.c
	conditions.c
	filters.c
	follow.c
	print.c
	ringbuffer.c

and other stuff in "util.c" is also used by the Ethereal and Tethereal
core, and contains no GUI code.

The rest of the stuff in the top-level directory is either

	1) implementations of routines used by Ethereal but not present
	   on all platforms (it contains no GUI code);

	2) files for the Ethereal core;

	3) files for other commands such as Tethereal, editcap, etc..