Android - Anything similar to the iPhone SDK Delegate Callbacks?

Question

I just switched over from iPhone to Android and am looking for something similar to where in the iPhone SDK, when a class finishes a certain task, it calls delegate methods in objects set as it's delegates.

I don't need too many details. I went through the docs and didn't find anything (the closest I got was "broadcast intents" which seem more like iOS notifications).

Even if someone can point me to the correct documentation, it would be great.

Thanks!

Answer 1

Never mind... found the answer here :)

http://www.javaworld.com/javaworld/javatips/jw-javatip10.html

---

Pasting from the article so as to preserve it:

Developers conversant in the event-driven programming model of MS-Windows and the X Window System are accustomed to passing function pointers that are invoked (that is, "called back") when something happens. Java's object-oriented model does not currently support method pointers, and thus seems to preclude using this comfortable mechanism. But all is not lost!

Java's support of interfaces provides a mechanism by which we can get the equivalent of callbacks. The trick is to define a simple interface that declares the method we wish to be invoked.

For example, suppose we want to be notified when an event happens. We can define an interface:

public interface InterestingEvent {     // This is just a regular method so it can return something or     // take arguments if you like.     public void interestingEvent (); } 

This gives us a grip on any objects of classes that implement the interface. So, we need not concern ourselves with any other extraneous type information. This is much nicer than hacking trampoline C functions that use the data field of widgets to hold an object pointer when using C++ code with Motif.

The class that will signal the event needs to expect objects that implement the InterestingEvent interface and then invoke the interestingEvent() method as appropriate.

public class EventNotifier {     private InterestingEvent ie;     private boolean somethingHappened;      public EventNotifier (InterestingEvent event)     {     // Save the event object for later use.     ie = event;      // Nothing to report yet.     somethingHappened = false;     }      //...       public void doWork ()     {     // Check the predicate, which is set elsewhere.     if (somethingHappened)         {         // Signal the even by invoking the interface's method.         ie.interestingEvent ();         }     //...     }      // ... } 

In that example, I used the somethingHappened predicate to track whether or not the event should be triggered. In many instances, the very fact that the method was called is enough to warrant signaling the interestingEvent().

The code that wishes to receive the event notification must implement the InterestingEvent interface and just pass a reference to itself to the event notifier.

public class CallMe implements InterestingEvent {     private EventNotifier en;      public CallMe ()     {     // Create the event notifier and pass ourself to it.     en = new EventNotifier (this);     }      // Define the actual handler for the event.     public void interestingEvent ()     {     // Wow!  Something really interesting must have occurred!     // Do something...     }      //... } 

That's all there is to it. I hope use this simple Java idiom will make your transition to Java a bit less jittery.

Answer 2

The pendant for kotlin.

Define your interface: In my example I scan a credit card with an external library.

interface ScanIOInterface {      fun onScannedCreditCard(creditCard: CreditCard) } 

Create a class where you can register your Activity / Fragment.

class ScanIOScanner {   var scannerInterface: ScanIOInterface? = null    fun startScanningCreditCard() {       val creditCard = Library.whichScanCreditCard() //returns CreditCard model       scannerInterface?.onScannedCreditCard(creditCard)   } } 

Implement the interface in your Activity / Fragment.

class YourClassActivity extends AppCompatActivity, ScanIOInterface {     //called when credit card was scanned     override fun onScannedCreditCard(creditCard: CreditCard) {         //do stuff with the credit card information     }      //call scanIOScanner to register your interface     override fun onViewCreated(view: View, savedInstanceState: Bundle?) {        super.onViewCreated(view, savedInstanceState)         val scanIOScanner = ScanIOScanner()        scanIOScanner.scannerInterface = this     } }  

CreditCard is a model and could be define however you like. In my case it includes brand, digits, expiry date ...

After that you can call scanIOScanner.startScanningCreditCard() wherever you like.