ember-old-router

Something I have noticed recently with Ember Router is it only allows navigating to leaf routes — routes without child routes. Now unless I'm doing things incorrectly then this seems like a bug/mistake in design. Let's take for example something like this: I have a collection of projects, each project has many collaborators, with this I want to build a UI with a 3 column layout (something like your standard desktop email client) where on the left I have a list of projects, when clicking on a project the middle column shows a list of collaborators, and clicking on a collaborator loads its

I'm sure this will become clear as I dig in deeper, but for now it's not obvious how to make this happen. I was following the info on this helpful SO article about routing but there is an important piece missing from the example, i.e. how do you get the 'home' view to render right away without having to click the 'home' link? I've started digging into the docs to try to make sense of this, but meanwhile it seems like a useful question to have answered for posterity. I've been playing with the working jsfiddle example from the above question here and comparing with this other example I found

Regarding the new Ember.js routing system (described here ), if I understand correctly, views are destroyed when you exit a route. Is there any way to bypass destruction of views upon exiting a route, so that the state of the view is preserved when the user re-enters the route? Update: Looks like, views are not destroyed unless the outlet view is being replaced in the new route. For e.g., if you are in stateA with ViewA in some {{outlet master}} and you go to stateB with ViewB in {{outlet master}}, then ViewB will replace ViewA. A way around this is to define multiple outlets when you need to

I'm trying to figure out how to handle invalid routes within my application using Ember.Router . Currently if I enter an invalid route, e.g. myapp.com/#FooBarDoesntExist, it will redirect to the index route ('/'). I'd like it if I could define a notFound or 404 state that it would route to so I can inform the user what happend. As opposed to them getting dumped on the home page. tokarev Ember.Router in its current version does not provide means to handle unknown routes. Time to hack! Solution 1 - Quick and dirty The idea here is the following. We have the Ember.Router.route(path) method, which

I was previously working with Ember.StateManager and now I'm doing some tests before I finally switch to Ember.Router , but I'm failing to understand how to properly bind my view data from the collection residing in my controller. I have a very simple testing structure with Ember.Router which is working fine navigation-wise , but when it comes to data binding it's not working as expected, and I confess I'm lost now. As for my data, I have a simple ASP.NET MVC4 Web API running a REST service which is working fine (I have tested with Fiddler and it's all good). Storing in SQL with EF4.* and no

I've asked a question previously in which I wanted to bind a collection residing in the controller to the list scenario view , however, I've added details and edit templates and views to my structure producing a couple of extra sub-routes: root.contacts.details -> /contacts/:contact_id root.contacts.edit -> /contacts/:contact_id/edit In my details scenarios I first started calling the connectOutlets as follows [...] connectOutlets: function (router, contact) { router.get('contactController').set('contact', contact); router.get('applicationController').connectOutlet('contacts'); },[...] This