Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>What mechanism should I use when communicating between views that are not in a child/parent hierarchy?</p> </blockquote> <p>In a typical ember application this communication should happen between controllers. Otherwise "Poor Option 2" is on the right track:</p> <blockquote> <p>Communication could be handled by a controller (and possibly even a model) that would hold properties that the toolbar sets and the "listening" view reacts to and resets the value of. </p> </blockquote> <p>Consider using two controllers. Toolbar actions will target the <code>ToolbarController</code>, which is responsible for maintaining the toolbar's state and for changing main in response to user action. <code>ToolbarController</code> should declare a dependency on <code>MainController</code> via the <code>needs</code> property. For example:</p> <pre><code>App.ToolbarController = Ember.Controller.extend({ needs: ['main'], buttonOneGotAllPressed: function() { main = this.get('controllers.main'); main.turnOffAnOption(); main.makeSomeOtherChange(); } }); </code></pre> <p>Now <code>MainController</code> can be focused on the state of MainView. It should not be aware of <code>ToolbarController</code> or it's buttons.</p> <blockquote> <p>This sounds like abuse of the controller and model purposes and like a pretty poor event listener setup.</p> </blockquote> <p>Agreed it would likely be an abuse of model purposes but it is exactly what controllers are for. </p> <p>This is definitely not an event-listener setup, but that does not seem a good fit in your case. The toolbar you describe seems to exist only to interact with the main view, so it makes sense to have a toolbar controller that depends on main and interacts with it directly. </p> <p>If the components are truly decoupled then an observer (Pub/Sub) pattern might be more appropriate. See <a href="https://stackoverflow.com/questions/14458287/how-to-fire-an-event-to-ember-from-another-framework/14508316#14508316">How to fire an event to Ember from another framework</a> if that's of interest.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to make an action affect a sibling view without controller.get('view')?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USMike Grassotti
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to make an action affect a sibling view without controller.get('view')?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis is some serious magic. I could not see any reference for using 'needs' property in the documentation. Ember is full of hidden surprises, I'm not sure if that's a good thing. Extremely hard to get a mental model of the whole framework. The most frustrating thing is that there's no clear definition of responsibilities of the classes.
      singulars
      1. PO
      1. USDenzo
    2. COAgreed, this is a very interesting feature. I would go this way immediately if I was changing some state in the main view. That could naturally be governed by a property on the controller. But when the thing I want to trigger on the view is more akin to "blink", "bounce" and such things I am feel less comfortable linking that to a property. E.G. It would be a property called "is_bouncing" that the controller would change to true and the view reset to false immediately upon seeing it being true. They would basically be booleans acting as triggers instead of representing any state.
      singulars
      1. PO
      1. USMartin Westin
    3. COAdding a note here for future reference: this is now documented http://emberjs.com/guides/controllers/dependencies-between-controllers/
      singulars
      1. PO
      1. USJordan Sitkin
 

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