Allow dynamic component control registration

[wombleton]

Expose registering components so that they can be registered after view initialisation.

[johnyanarella]

Good idea. I think this would work well, paired with another public method for unregistering dynamically added components. I will review this with the team.

[johnyanarella]

We're considering some options for how we can solve this issue and #5 such that the framework automatically handles the complexity of these common concerns for the developer.

Even so, I suspect we'll still want to expose public methods like you proposed to support less conventional use cases and manual optimization.

[johnyanarella]

In addition to the new live component selector syntax available in the Deft.mvc.ViewController's control annotation, I have also introduced the following new public methods to allow manual access to the same functionality:

Deft.mvc.ViewController::addComponentReference( id, selector, live = false )
Deft.mvc.ViewController::removeComponentReference( id )
Deft.mvc.ViewController::addComponentSelector( selector, listeners, live = false )
Deft.mvc.ViewController::removeComponentSelector( selector, live = false )
Deft.mvc.ViewController::getComponentSelector( selector )

Deft.mvc.ComponentSelector::addListener( eventName, fn, scope, options )
Deft.mvc.ComponentSelector::removeListener( eventName, fn, scope )

References, selectors and listeners are automatically cleaned up when the view (and consequently the ViewController) is destroyed.

This new feature is available in the code currently in the master branch and will be shipped as part of Deft JS v0.8.