Databases
StackOverflow2013
Postsdbo
PONested MVC communication patterns
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONested MVC communication patterns
    primarykey
    data
    text
    <p>This is entirely a best practices type question, so the language is irrelevant. I understand the basic principles of MVC, and that there are different, subtle flavors of it (i.e. views having a direct reference to models vs. a data delegate off the controller).</p> <p>My question is around cross MVC communication, when those MVCs are nested. An example of this would be a drawing program (like Paint or something). The Canvas itself could be an MVC, but so could each drawn entity (e.g. Shapes, Text). From a model perspective, it makes sense for the <code>CanvasModel</code> to have a collection of entities, but should the <code>CanvasView</code> and <code>CanvasController</code> have corresponding collections of entity views and controllers respectively?</p> <p>Also, what's the best/cleanest way to add a new drawn entity? Say the user has the CircleTool active, they click in the Canvas view and start drawing the shape. The <code>CanvasView</code> could fire relevant mouse down/move/up events that the <code>CanvasController</code> could listen to. The controller could then basically proxy those events to the CircleTool (state pattern). On mouse down, the CircleTool would want to create a new Circle. Should the Tool create a new <code>CircleEntityController</code> outright and call something like <code>canvasController.addEntity(circleController)</code>? Where should the responsibility of creating the Circle's model and view then lie?</p> <p>Sorry if these questions are somewhat nebulous :)</p> <p>--<strong>EDIT</strong>--</p> <p>Here's a pseudo-codish example of what I'm talking about:</p> <pre><code>CircleTool { ... onCanvasMouseDown: function(x, y) { // should this tool/service create the new entity's model, view, and controller? var model = new CircleModel(x, y); var view = new CircleView(model); var controller = new CircleController(model, view); // should the canvasController's add method take in all 3 components // and then add them to their respective endpoints? this.canvasController.addEntity(model, view, controller); } ... } CanvasController { ... addEntity: function(model, view, controller) { // this doesn't really feel right... this.entityControllers.add(controller); this.model.addEntityModel(model); this.view.addEntityView(view); } ... } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USchinabuffet
    1. USchinabuffet
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONested MVC communication patterns
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PONested MVC communication patterns
      1. UStmsimont
      1. VTFavorite
    3. VO
      singulars
      1. PONested MVC communication patterns
      1. This table or related slice is empty.
      1. VTUpMod
    1. COyou might want to take a look at: http://en.wikipedia.org/wiki/Mediator_pattern
      singulars
      1. PONested MVC communication patterns
      1. USRay Tayek
    2. COWhere would the Mediator exist for this scenario, and what would it look like? It seems like it could possibly work, but I'm not quite sure how it fits into the MVC triads. A mediator really just seems like a Controller (especially in the case of how Apple wants you to use MVC).
      singulars
      1. PONested MVC communication patterns
      1. USchinabuffet
    3. COtoo long, i will post an answer
      singulars
      1. PONested MVC communication patterns
      1. USRay Tayek
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload