I personally feel that these events should stay in the `init` method so we can keep the concerns separate. If we could convert the `currentPanel` property to a method we could then expose a promise to invert control back to the `init` method. Unfortunately this may be a risky move since there is a lot of code in settings that relies on the property nature of `currentPanel`.

In lieu of not being able to expose a callback, we could go a more decoupled route by emitting an event from `currentPanel` that `init` can listen for a single instance of this event in order to fire these other events. To me this would be preferred over having to create tracking flags in the settings app to determine whether or not these events have fired.

Thoughts?