On Tue, 04 Feb 2014 14:01:16 -0200, Christian Köberl
<tapestry.christian.koeb...@gmail.com> wrote:
I guess event handlers should be registered in completely different
way - using ids, CSS classes or "data-" attributes. More like the
standard jQuery way with selectors and "on":
$( "#myTable tr" ).on( "click", function() {
alert( $( this ).attr("data-id") );
});
That's what Tapestry 5.4 does in its components.
So, all the JS for a component should be in the JS.
But the JS file still needs to be included in the HTML.
So maybe the whole
JavaScriptSupport class should be deprecated?
How would JavaScript files be included by pages and components? Do you
have any suggestion on how a JavaScriptSupport-less Tapestry would work in
relation to JavaScript? I'm sorry, I just cannot see how (nor why).
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
