feat(require):add event listening

[frostbane]

This patch lets the required child listen to an event fired by the parent.

This is quite long and I am writing this while on my job (secretly) so my words could be jumbled. child, widget, feature, template all mean the same thing.

Syntax

The syntax is quite confusing until you get used to it

<!-- parent.html -->
<rv-require name="widget"
            data-listen-☆☆="△△"></rv-require>

☆ is the event fired inside the widget

△ is the event fired by the parent

One example is:

I have a html form

<!-- parent.html -->
<rv-require name="advancedWidget"
            data-title="show advanced settings.."
            data-listen-cleanupadvanced="reset-form"></rv-require>
<rv-require name="superAdvancedWidget"
            data-title="show super advanced settings.."
            data-listen-cleanupsuperadvanced="reset-form"></rv-require>
<input type="reset"
       value="reset everything"
       on-click="reset-button" />

Now when I hit the reset button I would do some clean up and and also need to tell all the required widgets to do their own clean up.

//parent.js

//fired when the reset button is clicked
parentRactive.on("reset-button", function(e){
    //clean up the form

    var args = { /*some argument */ };

    //broadcast it to all the required children
    parentRactive.fire("reset-form", args);
});

And then all the listening children could respond to it accordingly.

//advancedWidget.js

advancedWidgetRactive.on("cleanupadvanced", 
    function(parentEventName, eventArgs){
        //in this example the handler arguments would be
        //parenEventName = "reset-form"
        //eventArgs      = { /*some argument */}

        //do some cleaning inside the widget
    });

//superAdvancedWidget.js

superAdvancedWidgetRactive.on("cleanupsuperadvanced", 
    function(parentEventName, eventArgs){
        //in this example the handler arguments would be
        //parenEventName = "reset-form"
        //eventArgs      = { /*some argument */}

        //do some cleaning inside the widget
    });

The main point is I could fire a single "reset-form" event inside the parent and all the required children would just listen to it, and respectively do their own clean up.

Another way to call it is broadcast or propagate an event to all children.

[frostbane]

@XavierBoubert

I just added this today, it could still have some bugs.

Please give me until friday to test it.

[XavierBoubert]

Sure

[frostbane]

@XavierBoubert

There seems to be no problems.

You can merge it anytime. d=(^o^)=b

[XavierBoubert]

Nice. I take a look this weekend and I merge it ;-)

[XavierBoubert]

I think it's

parent.on(event, function() {

[XavierBoubert]

No it's ok, my bad.

[XavierBoubert]

The syntax is quite confusing until you get used to it

Exactly lol.

[XavierBoubert]

Merged and released in 0.6.3 ;)