This may help. Compare these:
T5.3:
http://jumpstart.doublenegative.com.au/jumpstart/examples/javascript/javascript
<http://jumpstart.doublenegative.com.au/jumpstart/examples/javascript/javascript>
T5.4:
http://jumpstart.doublenegative.com.au/jumpstart7/examples/javascript/javascript
<http://jumpstart.doublenegative.com.au/jumpstart7/examples/javascript/javascript>
T5.3:
http://jumpstart.doublenegative.com.au/jumpstart/examples/javascript/robust
<http://jumpstart.doublenegative.com.au/jumpstart/examples/javascript/robust>
T5.4:
http://jumpstart.doublenegative.com.au/jumpstart7/examples/javascript/robust
<http://jumpstart.doublenegative.com.au/jumpstart7/examples/javascript/robust>
T5.4:
http://jumpstart.doublenegative.com.au/jumpstart7/examples/javascript/modal/1
<http://jumpstart.doublenegative.com.au/jumpstart7/examples/javascript/modal/1>
Geoff
> On 27 Sep 2015, at 8:17 am, David Taylor <[email protected]>
> wrote:
>
> Hello,
>
> We are working on several Tapestry 5.4 applications that make extensive use
> of Kendo UI components in addition to the standard Tapestry components. We
> have created Tapestry components wrapping the Kendo UI components, but see
> that the JavaScriptSupport methods we are using in setupRender() to emit our
> JavaScript have been marked as deprecated. The remaining non-deprecated
> JavaScriptSupport methods do not appear to provide the functionality needed
> to dynamically assemble the required Kendo UI Javascript initialization logic
> (e.g. http://docs.telerik.com/kendo-ui/framework/datasource/overview).
>
> What mechanisms exist in Tapestry 5.4 that can be used to replace the
> functionality of the deprecated addInitializerCall() and addScript() methods?
> The remaining methods in JavaScriptSupport seem to be focused on the use of
> static JavaScript files which does not work well for heavily
> JavaScript-driven component sets such as Kendo UI or jQuery UI.
>
> While the approach we are currently using works well, it is clearly not
> supportable long term given the Tapestry method deprecations. Any feedback on
> how this logic should be structured in Tapestry 5.4 would be greatly
> appreciated.
>
> --
> David Taylor
> http://www.extensiatech.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
