Gerald Combs wrote:
Enough major changes have been introduced since the last release to
warrant bumping the minor revision. I figure we may as well bump it to
0.99.0 in order to prepare for an impending 1.0 release.
Will the 1.0 release promise a stable API/ABI for plugins?
If so, I'd prefer that said API/ABI not be the current one. Among other
things:
1) lengths in various tvbuff calls are signed, and -1 means "to the end
of the tvbuff", which means that we have to do special stuff (such as
tvb_ensure_length_remaining() calls) to handle 32-bit length fields, as
those fields might have the topmost bit set;
2) tvb_new_subset() should really have only one length argument, the
"reported length" value, with the "actual" length value computed based
on the "reported length" value and the "actual" length value of the
parent tvbuff;
3) strings need to be handled differently, with a string value perhaps
having:
a character encoding type;
a "raw" value, which is just a copy of the bytes from the packet;
a UTF-8 value or perhaps a UTF-16 value, for display, filter tests,
etc. (we only compute that if we need it);
to better handle non-ASCII text;
etc.
If the Wiretap API/ABI is also to be made stable, it should be ready to
handle pcap-NG, even if it doesn't have pcap-NG support; there are
changes we'd want for that (e.g., support for comments in capture files
- there are some other capture file types that could use that - and
support for the information about network interfaces in the capture file).
Along with the items in http://wiki.ethereal.com/Development/Roadmap I'd
like to do the following before 1.0:
...
- Smooth out the Windows file dialogs: The "Filter" button doesn't
work, for instance.
We might want to fix up dialog handling in general. The GTK+ file
chooser, and the Windows file dialog, are modal; we should probably make
the older one modal as well. Some other dialogs, such as simple
dialogs, should perhaps also be modal.
