Databases
StackOverflow2013
Postsdbo
POEmber.js and it's automagic properties / conventional behaviour
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEmber.js and it's automagic properties / conventional behaviour
    primarykey
    data
    text
    <p>I recently discovered ember.js and it caught my interest for it's sophistication and possibilities. I went through several learning materials so far:</p> <ul> <li><a href="http://emberjs.com/guides/" rel="nofollow">Ember.js' own guides</a></li> <li>Several source codes (e.g. <a href="https://github.com/emberjs/todos" rel="nofollow">sample ToDo app</a>)</li> <li><a href="https://www.youtube.com/watch?v=4Ed_o3_59ME" rel="nofollow">Presentations from Tom and Yehuda</a></li> </ul> <p>From these, I understood that there is a lot of "assumptions" about how the framework should be used, how should we name views, controllers and models and that <strong>if we follow these conventions</strong>, we can save a lot of code typing because <strong>Ember.js can do that "out of box", by default.</strong></p> <p>This is, of course, extremely handy, but only in the case when you really know WHAT is happening behind the scenes for you that you did not have to write. And from that come my questions:</p> <p><strong>WHAT</strong> is happening when we define one application template and one view, for example? What is done for us automatically? Is the applicationController instantiated for us? Or, do we have to create one manually? What about any other view / controller pairs that are not applicationViews/Controllers, like a subview (since applicationView and applicationController are somehow unique in that they MUST be present in any ember.js app ) ?</p> <p><strong>WHAT</strong> does the router ( API from 1.0pre4 ) do automatically for us if we only define a bunch of routes but do not override any of the router's default, conventional behaviour?</p> <p>Personally, what would really help me understand the key concepts here is a <strong>sample application</strong> with a transition to another state <strong>that would implement everything the application needs to do in order to work properly</strong> ( meaning, it would not depend on any code that ember would do for us otherwise ). That way, I would be able to see the various parts at play and "re-engineer" the process in my head and, hopefully, understand the process in its completeness.</p> <p>If this question is overly complex or vague please suggest how I could narrow down my interest.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKara
    1. USRobert Rossmann
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEmber.js and it's automagic properties / conventional behaviour
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POEmber.js and it's automagic properties / conventional behaviour
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POEmber.js and it's automagic properties / conventional behaviour
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COThe ember.js peepcode episode explains this very well and it will only set you back 12 bucks: https://peepcode.com/products/emberjs
      singulars
      1. POEmber.js and it's automagic properties / conventional behaviour
      1. USklaaspieter
    2. COI just was about to ask the same question...
      singulars
      1. POEmber.js and it's automagic properties / conventional behaviour
      1. USJanD
 

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