--- On Thu, 3 Jun 1999 16:22:05 -0700 (PDT) Guy Harris <guy@xxxxxxxxxx>
>...none of which *requires* the Xrm mechanism. In fact, if the program
True!
>isn't an X application, the Xrm mechanism might not even be *available*
>for that purpose. (And, yes, non-X Ethereals might want to support
>color; consider, for example, a "curses"-based one, on a color
>terminal/color "xterm".)
Yep.
>I wouldn't expect Ethereal to have default colors for packet types other
>than "black"; I'd expect a model like Network Monitor, wherein I'd pull
I have rarely used Network Monitor. I have used LanWatch a lot and it has
default colors. They may not even be changable.
>up, say, the "Preferences" dialog box, and select a protocol from a
>scrolling list and then choose a color for it (from a NetMon-like
>drop-down list, or from a GTK-style color picker - perhaps provide a
>simple palette from something like a drop-down list, and let them pop up
>the Full Frontal GTK Color Picker if they ask for it?).
The dropdown seems like a nice feature, but the Color Picker seems like a bit
of overkill. And there is nothing preventing using any of these schemes with
Xrm, BTW.
>
>Given that, I'm not sure something like the Xrm mechanism would buy you
>anything, other than *maybe* not having to add parsing code to handle
>color specifications in a ".ethereal/preferences" file.
So. Is there some non-Xrm resource scheme you (or anyone else reading this)
has used which has these features? I guess the real features we need are some
sort of heirachry of files, persistance available from the API, and readable
configuration files. Any others?
--john
-------------------------------------
Name: John McDermott
VOICE: +1 505/377-6293 FAX +1 505/377-6313
E-mail: John McDermott <jjm@xxxxxxxxxx>
Writer and Computer Consultant
-------------------------------------
