Ember.ContainerView • Templates can’t always describe all UI • Sometimes more flexibility is required • ContainerView holds other view instances, allows code to add, remove, reorder • set currentView property • or manage childViews array
Result • Controller is context for a chunk of DOM • Controller is good place to have properties that many views access • Reduces need to bind lots of values to the views themselves • Moving things around in templates is easier
Creating helpers • Main issue is having bindings work within your helper’s output • Easiest path: call one of the other helpers from your helper after some setup • Future: easier ability to bind some types of helpers (see PR 615)