Databases
StackOverflow2013
Postsdbo
POBackbone Marionette using Require.js, Regions and how to set up
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBackbone Marionette using Require.js, Regions and how to set up
    primarykey
    data
    text
    <p>I'm currently writing a Backbone Marionette app which ultimately amounts to about 6 different "screens" or pages which will often times share content and I am unsure of how to best structure and access Regions.</p> <p>I am using the app/module setup described here: <strong><a href="https://stackoverflow.com/questions/11070408/how-to-define-use-several-routings-using-backbone-and-requirejs">StackOverflow question 11070408: How to define/use several routings using backbone and require.js</a></strong>. This will be an application which will have new functionality and content added to it over time and need to be scalable (and obviously as re-usable as possible)</p> <p>The Single Page App I'm building has 4 primary sections on every screen: Header, Primary Content, Secondary Content, Footer.</p> <p>The footer will be consistent across all pages, the header will be the same on 3 of the pages, and slightly modified (using about 80% of the same elements/content) on the remaining 3 pages. The "morecontent" region will be re-usable across various pages.</p> <p>In my app.js file I'm defining my regions like so:</p> <pre><code>define(['views/LandingScreen', 'views/Header', 'router'], function(LandingScreen, Header, Router) { "use strict"; var App = new Backbone.Marionette.Application(); App.addRegions({ header: '#mainHeader', maincontent: '#mainContent', morecontent: '#moreContent', footer: '#mainFooter' }); App.addInitializer(function (options) { }); App.on("initialize:after", function () { if (!Backbone.History.started) Backbone.history.start(); }); return App; }); </code></pre> <p>Now, referring back to the app setup in the aforementioned post, what would be the best way to handle the Regions. Would I independently re-declare each region in each sub-app? That seems to be the best way to keep modules as independent as possible. If I go that route, what would be the best way to open/close or hide/show those regions between the sub-apps? </p> <p>Or, do I keep the Regions declared in app.js? If so, how would I then best alter and orchestrate events those regions from sub-apps? Having the Regions defined in the app.js file seems to be counter-intuitive to keeping what modules and the core app know about each other to a minimum. Plus, every example I see has the appRegions method in the main app file. What then is the best practice for accessing and changing those regions from the sub-app?</p> <p>Thanks in advance!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USmindpivot
    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
    1. VO
      singulars
      1. POBackbone Marionette using Require.js, Regions and how to set up
      1. USLeonardo
      1. VTFavorite
    2. VO
      singulars
      1. POBackbone Marionette using Require.js, Regions and how to set up
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POBackbone Marionette using Require.js, Regions and how to set up
      1. USmindpivot
      1. VTFavorite
    1. COSorry for the delay, I've been debating AMD vs non-AMD based on the two answers I've gotten. For long-term plans, despite the fact I feel like I'm spending more time figuring out managing dependencies than the functionality of my app, it is going to be preferable to go the AMD route.
      singulars
      1. POBackbone Marionette using Require.js, Regions and how to set up
      1. USmindpivot
 

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