Laurent Deniel wrote:
Ulf Lamping wrote:
What doc do you think of? The only doc I know of this is the user's
guide.
And the manual page ?
Forgotten that. Well, a manual page for a GUI is an anachronism IHMO
(but that was discussed earlier on the list).
However, I will update the manpage about the capture dialog and the menu
changes I've recently done. I will also have a look at the "onboard help".
If I understand you correct, you want to have only one ring buffer
file, with unlimited number of switches to the next (the same file
again, but emptied out).
What is the use of *one* ring buffer file? It will be overwritten at
the next file switch so your complete history get's lost at some
point in time.
Right, and this is exactly what I want in some cases (i.e. *one* file
which
is limited in size). But not so important than the "unlimited" case.
Again, what is the *use* of only one ring buffer file? What is it
helpful for?
You cannot use it with the "Update list of packets in realtime" option,
so it won't be helpful to have something like an unlimited "display
only" capture.
And if you stop capturing at the "right" moment, your file will be
empty, so you won't get any valuable data from the capture.
That's exactly the trap I wanted to avoid for first time users, as I
didn't saw a use case for a single ring buffer file.
The '0' in the GUI was only temporary since I wanted to have the core
features in place very quickly and without spending then too much time
in the GUI part ...
I'm a bit angry about that. Being translated this would mean:
"If anyone else cannot use or understand my GUI , that his own
problem. Should someone else may do the work of fixing the GUI."
No, this means that when I have the time (or when someone else cares) to
enhance it (and you care ;-). But remember that changing / beautifying
things is
OK as long as you don't remove features used by end users for years.
That's one of the problems when you do changes on existing things.
This is a pattern: Implementing some new feature, and putting it
"somehow" into the GUI, so all features can be accessed in a way.
That's exactly (one of?) the reason why ethereal has a bad reputation
when it comes to usability.
One other is the lack of decent help / doc (or mismatch of real
implementation and doc ;-) ...
ACK
That's one of the reasons that I want to update the user's guide, but
didn't found an easy way of doing so :-(
and stability of GTK or Ethereal GUI code.
I didn't hear any real complains about stability in the past.
Regards, ULFL
