Hey, I have found myself using the same pattern quite often, where I would have an ActorSystem inside an Activity and then use an Actor per each Fragment. Since the fragments can be created and destroyed throughout the activity lifecycle, they are attached to and detached from these actors. So in effect, we have a robust message-passing system, and can manipulate the UI—when it’s active—from inside the actors. Here it is: https://github.com/stanch/akka-fragments It also helps avoid some of the pitfalls with ProGuard and ClassLoaders, as discussed above.
Nick -- You received this message because you are subscribed to the Google Groups "scala-on-android" group. To unsubscribe from this group and stop receiving emails from it, send an email to scala-on-android+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
