Best practices for ember subnavs

[eccegordo]

You may want to try using a component for this. And have the component render into a named outlet in your main application template.

The nice thing is that the component can be dropped in and shared in all sorts of places, and the context (controller and models) can be passed into it making it a very flexible construct.

In handlebars the component

{{sub-nav}}

I worked out a a basic example of components here.

Events in an ember view

This may be a gross misunderstanding of the view concept in Ember… But is it possible for a view to capture the action events in its template before they hit the controller or route? Maybe this kind of behavior really belongs in a component? Are views limited to the kind of events they can receive? e.g. the built in events (click, drag, mouseOver, etc) Does a view like this make sense? App.RequirementsView = Ember.View.extend({ templateName: 'requirementsview', events: { sel…

If you could put together a basic JSBin of the concept you are trying to achieve, I could take a stab at this.