I have a sneaking suspicion that trying to implement this you would end up
writing a custom implementation of <script> and eval(...) to achieve
tapestry's current behaviour
:)
On 4 Feb 2014 16:01, "Christian Köberl" <
tapestry.christian.koeb...@gmail.com> wrote:
> 2014-02-04 Lance Java <lance.j...@googlemail.com>:
> >>> How would you propose JavaScriptSupport.addScript(...) would work
> without inline scripts?
> >> Not to mention that JavaScriptSupport.addScript() is deprecated.
> > The same question applies to JavaScriptSupport.require(...)
>
> 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") );
> });
> So, all the JS for a component should be in the JS. So maybe the whole
> JavaScriptSupport class should be deprecated?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
