Yeah I use 'em in a Pivot app I wrote, and another benefit is that you
can use the @Override attribute on the methods you override, and then
if we change the listener interface, the compiler tells you :)

I like the concept, but things to consider:

1) Where would they go?  In the same package as the interface itself?

2) How much does this bloat the JAR files that we release?

-T

On Fri, Apr 10, 2009 at 4:26 PM, Noel Grandin <noelgran...@gmail.com> wrote:
> Hi
>
> Are there plans for Adapter classes for the various listener interfaces?
> I realise that it is a lot of pretty boring classes, but they're
> really useful for
> (a) not having to update code when methods are added to listener APIs
> (b) only implementing the exact events that you're interested in.
>
> I'll volunteer to produce a patch for this :-)
>
> Regards, Noel Grandin
>

Reply via email to