On Sun, 2003-11-16 at 19:31, Ulf Lamping wrote:
> I like the GKT2 GUI, as it is much nicer to look at. It would also
> make things easier, get rid of a lot of #ifdefs,using the glade, ...
>
> Unfortunately, a GTK1 GUI is still needed at least for the current
> win32 port. I'm testing regularly with it, and it's *really* slow. So
> until we have acceptable speed for GTK2 on win32, we should keep the
> "dual GUI" option. And of course, we must have a look at the other
> supported platforms as well.
> This concept could be somewhat easily implemented by using handlebars
> for the three main panels. Have a look at the latest 0.9.16 release.
> The toolbar is using this handlebars, so it can be moved out of the
> main window and put anywhere on the screen as a seperate window. That
> might be what you want.
> (Note: I've removed this handlebar in the latest CVS, as I could not
> see a reason to use this feature for the toolbar).
>
Hmmm the normal handlebars don't work that nice, since you can not
easily dock the bar on a other place than the original place.
> I like the gimp, but I don't like the Gimp window concept, as it will
> put at a lot of windows to your screen by default, this usually
> confuses users a lot. By using handlebars, the program will start in a
> single window, and the user can place the panels somewhere on the
> screen as he likes.
The concept works very well when having two monitors (there the current
Ethereal concept fails, i have the screen space but can't use it).
> Well, as you stated yourself, Ethereal is a GTK, but not a gnome
> application (and GTK is ported to MS-Windows). So the gnome HIG is
> suitable in lot's of points. But some of the things in the HIG are
> uncommon. Like the button layout of dialog boxes (e.g. to put the ok
> button straight to the right).
>
When Ethereal runs on OS/X, WIN32, GNOME, KDE, etc. wouldn't it be an
idea to make true native GUI's for those systems and following the HIG's
for those systems ? As far as i know the GUI is rather separate from the
core functionality anyway ? Or maybe even make the Ethereal core in
such a way that it itself is a plugin, and hat it has no GUI at all. The
GUI's would than be a separate program that load the ethereal plugin?
The TUI would work in the same way, also just loading the ethereal
plugin. This would also make it easy for people to write for example a
KDE (or any other native toolkit ) version of ethereal.
> Of course it would be a good thing, when all dialogs would look
> similar :-), but this isn't a problem of an interface guideline, but
> only because lot's of different people have implemented their dialog
> as good as they can.
>
> Regards, ULFL
- Erwin
--
Erwin Rol Software Engineering - http://www.erwinrol.com/
