1. Domino Brix
2. Presenter lifecycle
3. Reveal & slots

Reveal & attach

• Resolve the slot via getSlotKey(); if missing, wait for onSlotRegistered.
• Run onBeforeRevealed() → slot reveal(view) → onRevealed().
• Attachable views (BrixView) notify onAttached()/onDetached(), triggering registerSlots(), onReady(), and onRemoved().

Registering slots dynamically

Override registerSlots() to add presenter-scoped slots; Brix cleans them up during deactivation.

			@BrixPresenter
@BrixRoute("dashboard")
@BrixSlot(BrixSlots.BRIX_BODY_SLOT)
public class DashboardPresenter extends Presenter<DashboardView> {
  // No manual view binding needed
}

@UiView
public class DashboardView extends BrixView<Element, DashboardHandlers>
    implements DashboardPresenter.DashboardView {
  @Handlers DashboardHandlers handlers;
}

		

Multiple reveals?

The presenter guards against duplicate activation. Reveal retries only when the slot becomes available; call reveal() manually if you need to reattach after state changes.