Repository navigation
Convenience for anonymous BroadcastReceivers #484
Description
Activity
AndroidAnnotations can only generate subclasses. Sorry but this doesn't look like anything AndroidAnnotations can do.
Why not? For the @EReceiverMethod approach, in an activity or fragment where some method is annotated as suggested above, AndroidAnnotations could generate the anonymous BroadcastReceiver in the subclass with a series of if statements to call the methods in the parent class. We could even attempt to extract extras from the intent based on the variable name and type in the method signature, if we want to get really fancy.
Well, the problem is here :
BroadcastReceiver mReceiver = new BroadcastReceiver(). This is an anonymous class. One cannot generate a subclass of an anonymous class. And even if we could, there's no way to replace thenew BroadcastReceiver()with anew BroadcastReceiver_(). Furthermore, we cannot access the variable name.Do you need to generate a subclass of the Receiver? The first proposal
would simply generate code in the onPause/onResume to register/unregister
the created receiver. The second proposal would generate the anonymous
receiver itself, transparent to the parent class.On Wed, Feb 27, 2013 at 11:59 AM, Pierre-Yves Ricau <
notifications@github.com> wrote:Well, the problem is here : BroadcastReceiver mReceiver = new
BroadcastReceiver() . This is an anonymous class. One cannot generate a
subclass of an anonymous class. And even if we could, there's no way to
replace the new BroadcastReceiver() with a new BroadcastReceiver_().
Furthermore, we cannot access the variable name.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/484#issuecomment-14185229
.
It would be excellent to be able to do something like this inside a fragment or activity:
And have AndroidAnnotations fill in the
registerReceiver()withIntentFilterinonResume()(oronCreate()) andunregisterReceiver()inonPause()(oronDestroy()).Or, even better, just annotate methods:
and have the receiver arg be optional, in case you're using sticky broadcasts, or something.
I'd love to work on this when I find time, just looking for input on the best way to approach it, IE: when to register/unregister, should that be an argument to the annotation, do we want to annotate methods, or just the object, etc.