support passing arguments to methods

[jkroso]

e.g:

<div>{render(items)}</div>

This almost works already but is just a little broken since it gets transformed to

'<div>' + model.render(call(model, view, 'items')) + '</div>'

where's what I wanted was to call the view's render method.

The use case is to make it easier to jump back to JS when you need the power. Though it could be used in place of computed properties in some cases.

[cristiandouce]

This would also be nice combined with what I just described on a comment at #140
link to comment

That way at a on-click binding you wouldn't have to query the DOM to get some data-something saved. You just could on-click="select(name)" and then

View.prototype.select = function (ev, name) { // ev should always be passed first IMO
   this.view.set('current', name)
}

No need for var name = dom(ev.target).getAttribute('data-name')...

[defunctzombie]

The issue with passing arguments to events is dealing with iteration. Currently, the second argument to an event handler is the reactive instance for the iterated item. This allows for implementing lists with delete buttons and access to the iterated instance. Maybe looking at home some other libs are handling this could provide some insight.

I think the original posted issue could be made to work tho and will see if that is the case without too much pain.