Alvaro Sanchez-Mariscal wrote:
Surely I can use Dojo 1.0 with theme="simple". But in that case, I
will not leverage Dojo Struts Tags in the server side.
What I would like is to use the s:* (or sx:*) tags rendered with Dojo
1.0. And in the cases where there is not a suitable tag, I will have
the chance to use "raw Dojo".
Yeah, that right. It would be convenient if tags existed for 1.0
already but there's none. It'll takes someone with a lot of familiarity
with Dojo 1.0 to be able to build useful reusable tags like the current
dojo plugin so I expect it'll take a while. However, if you use "raw
Dojo" instead and find you start re-using a lot of similar JS code, then
that code's an excellent starting point for a new sx:tag and you'll
probably be the best person to contribue it to struts2!
I only mentioned this because I've recently went through the same
process with YUI. I converted an existing Struts2.0.x application from
Dojo 0.40 to YUI 2.3.8. I started with the struts2-yui-plugin and added
yui:div, yui:submit, yui:a tags [1] because I wanted to minimise change
and reuse the existing JSP as much as possible. That works, but what
I've realised is that it's better to use the library as intended (in
YUI's case, writing OO javascript NOT mixed in with HTML) rather than to
hide the client-side functionality behind tags. ie. the tabbed panels,
datagrids and chart widgets are better suited to JS than generic tags. I
imagine the same would be true for Dojo because it's an exceptionally
powerful library and tags simple can't represent the usefulness of its API.
[1] http://code.google.com/p/struts2yuiplugin/issues/detail?id=4
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
