Wireshark-dev: Re: [Wireshark-dev] Ready to remove all non-ui-manager code?

From: Anders Broman <a.broman@xxxxxxxxxxxx>
Date: Thu, 15 Sep 2011 21:35:31 +0200
Chris Maynard skrev 2011-09-15 21:13:
Joerg Mayer<jmayer@...>  writes:

would it be OK to remove the non-UI-MANAGER code in gtk/?
I haven't seen any ongoing work in that area, so what (if anything) is
missing from the UI-MANAGER codebase?
The only things that come to my mind are the proto_help stuff and the
gtkvumeter stuff. The proto_help stuff isn't really cared for by its
original author and so far nobody has stepped up to convert it. If I
remember the discussion about gtkvumeter correctly, it may be either
removed or replaced by some other vumeter.
Are there any other points?
If there are no convincing arguments and nobody beats me to it, I'll remove
the old stuff about a week from now.
Personally, I'd like to see the proto_help stuff be supported again, but
unfortunately I don't have enough gtk knowledge to accomplish this myself in the
near future.

My interest is not so much with Inacon (although their freely available protocol
help is very good, in my opinion), but more with being able to provide at least
some free apropos protocol help whether it's from Inacon, Wireshark's wiki, or
from elsewhere.  To that end, I opened bug 4870[1].  What I still don't know is
how to best integrate/distribute the free Inacon and alternate help files I
provided with Wireshark, assuming of course that they would be useful to others
as well - perhaps not so much to those monitoring this list, but in particular
to Wireshark and protocol analysis newcomers.

[1] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4870
If we remove the the non-UI-Manager could we could leave the protocol help #if 0:d out or something like that until such a time when some one revives it again. It's not like it'll be gone forever. As code gets added
it's a fair chance Wireshark won't compile without UI_MANAGER.
Regards
Anders

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list<wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe