Shows one line (or one question) and resolves once the player is done with it.
This is the seam that keeps mwg/rpg free of a renderer. EventRunner used to construct a
ui.MessageBox and push it onto a ui.WindowStack itself, which meant an event interpreter
pure control flow over GameState - dragged the whole 2D widget layer in behind it, and
a game presenting dialogue any other way (a 3D scene, a DOM overlay, a test harness
asserting on script order) could not use it at all. two-d/ui's messageBoxPresenter is
the ready-made implementation, so nothing about the common case got harder.
Shows one line (or one question) and resolves once the player is done with it.
This is the seam that keeps
mwg/rpgfree of a renderer.EventRunnerused to construct aui.MessageBoxand push it onto aui.WindowStackitself, which meant an event interpreterGameState- dragged the whole 2D widget layer in behind it, and a game presenting dialogue any other way (a 3D scene, a DOM overlay, a test harness asserting on script order) could not use it at all.two-d/ui'smessageBoxPresenteris the ready-made implementation, so nothing about the common case got harder.