This document describes the structure and components of a Marionette dialog application, including layouts containing regions and views, the use of controllers, templates, and an app router. The application makes use of Marionette features like regions, triggers, events, and request-response communications to manage the dialog views and their contents in a composite structure.
1 of 1
More Related Content
Diagram
1. Dialog Application
@MM.module
dialog-app.coffee
show-controller.coffee
The Brain
App Wide Events
Marionette.RequestResponse
Async, Global Events
API
Async, Local Events
Views
Layout is an ItemView hybrid
Layout is a collection of Regions
Regions contain Views
Views optionally contain ItemViews
Layout(s)
Region(s)
View(s)
Composite Collection ItemView
Start/Stop
regions (sub-region de?nition)
events (view speci?c JS events)
triggers (view speci?c JS events)
ui (explicit UI nodes)
modelEvents
collectionEvents
onShow / onClose / on*
custom methods
template (CompositeView)
id (container ID)
className (container class)
itemViewContainer (itemView class)
itemView (itemView)
Class
extends Marionette.*
Directory Structure
scripts
apps
dialog
show
templates
views
dialog-app.coffee
show-controller.coffee
dialog.html
dialog.coffee
App Router
Marionette.AppRouter