StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15870472
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-04-08T02:45:25.817
FavoriteCount
0
LastActivityDate
2013-04-08T02:45:25.817
LastEditDate
LastEditorUserId
0
OwnerUserId
844923
ParentId
15870181
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
<p>You can use a generic <code>{{action }}</code> in your template but have the specifics of the "go back" implemented in the router. This works because Ember <a href="http://emberjs.com/guides/templates/actions/#toc_target-bubbling">bubbles up</a> the <code>goBack</code> event first to the controller, then the current route, then the parent route, etc, until an action handler is found. In this case, there is no matching action on the controller, so it is handled by the current route. This keeps your template/view/controller agnostic to the specifics, but when you are hooking up the widget you can specify how the "go back" should be handled.</p> <p>In the example the same button causes the route to change to different routes depending on which route is the current route:</p> <ul> <li>in route <code>/posts</code> the back button transitions to <code>/</code></li> <li>in route <code>/posts/new</code> the back button transitions to <code>/posts</code></li> </ul> <p><a href="http://jsbin.com/emakuh/1/edit">JSBin example</a></p> <p>Javascript:</p> <pre><code>App = Ember.Application.create({}); App.Router.map(function() { this.resource('posts', function() { this.route('new'); }); }); App.PostsRoute = Ember.Route.extend({ events: { goBack: function(){ this.transitionTo('index'); } } }); App.PostsNewRoute = Ember.Route.extend({ events: { goBack: function(){ this.transitionTo('posts'); } } }); </code></pre> <p>Template:</p> <pre><code><script type="text/x-handlebars" data-template-name="index"> <h2>Index Content:</h2> {{#linkTo posts}}Posts{{/linkTo}} {{outlet}} </script> <script type="text/x-handlebars" data-template-name="posts"> <h2>Posts</h2> <button {{action goBack}}>Go back</button> {{#linkTo posts.new}}New{{/linkTo}} {{outlet}} </script> <script type="text/x-handlebars" data-template-name="posts/new"> <h2>Posts/New</h2> </script> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGetting parent route in EmberJS
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCraigTeegarden
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. COGreat answer - thanks! I've marked @Unspecified's as accepted because it will involve less setup for each new route I add - but this would have been a perfectly good implementation, so thanks :)
  singulars
  PostPostId
  PO
  UserUserId
  USiHiD

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.