Just dissector. The GUI plugins are really tied to the GUI front-ends. I
suppose all plugins need a well-defined API... but my main interest is the
back-end stuff.

Gilbert

On Thu, Jul 12, 2012 at 1:46 PM, Richard Sharpe <[email protected]
> wrote:

> On Thu, Jul 12, 2012 at 10:16 AM, Evan Huus <[email protected]> wrote:
> > On Thu, Jul 12, 2012 at 11:01 AM, Gilbert Ramirez <[email protected]>
> > wrote:
> >>
> >> Also on my wish list is a rigorously-defined plugin API, with its own
> >> versioning, so that 3rd party plugin writers can know which versions of
> >> wireshark their plugins will work with.
> >
> >
> > This has been on my wish-list for a while now [1], so I'm very much
> looking
> > forward to what you come up with. Unfortunately my main development
> machine
> > is also Linux, so I can't help with cross-platform very much.
>
> Are you referring here to dissector plugins only, or GUI plugins as well?
>
> --
> Regards,
> Richard Sharpe
> (何以解憂?唯有杜康。--曹操)
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <[email protected]>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:[email protected]
> ?subject=unsubscribe
>
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to