Geoff,
Thanks for the 5.3/5.4 comparison links. Seeing non-trivial working
examples definitely clarified a few points for me regarding the new
approach. The modal dialog example is also very interesting in its own
right.
Looking at the examples, it seems the new module approach would require
us to develop some form of client-side JavaScript API to create the
necessary Kendo UI configuration objects. Parametrizing all of the
possible Kendo configuration options to work within the constraints of a
static JavaScript library would not be an easy task. The Kendo
configuration is very flexible and varies by component. Perhaps it would
be possible using a multi-step configuration approach, but I imagine
that wouldn't be very pretty.
Currently we generate the JavaScript code server side and emit it into
the page using the deprecated addScript() method. This allows us to
construct the Kendo JavaScript configuration taking into account the
configuration of the associated Tapestry-Kendo wrapper components and
data source information from our middle tier. The details of the
JavaScript code being generated are rather dynamic so it does not lend
itself to a static configuration approach.
Barring any additional approaches, it seems the addScript() method is
currently the most workable option. Does anyone know why this method was
marked as deprecated? Any chance it could be removed from the
deprecation list?
--
David Taylor
http://www.extensiatech.com
emailsig
On 9/26/2015 9:24 PM, Geoff Callender wrote:
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 <david.tay...@extensiatech.com> 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: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
