Is it likely that Tapestry 5 will move towards such a solution?
Could it even be suggested that one should be able to disable all
default Tapestry JS-code?
And even more out on a limb, would it be possible to put
Ajax/dhtml-support in a seperate module so as not to polute the codebase
with it? (Or alternatively supply an unpoluted core-package)
The reason I ask is because my Java-coding skill aren't near as solid as
my javascripting skills and in general my opinion of how ajax is handled
in frameworks is far from flattering. However with so many (hijax, dojo,
prototype, jquery, xml vs json, etc...) ways to skin a cat, I 'd rather
be able to obtain the plain and simple cat and do the skinning myself.
Anyway, the jira-comment at least makes me hopefull that more control of
the client-side behaviour may be in the making.
Kristian Marinkovic wrote:
hi borut,
have you read the comments on
https://issues.apache.org/jira/browse/TAPESTRY-1650
g,
kris
"Borut Bolčina" <[EMAIL PROTECTED]>
24.09.2007 14:34
Bitte antworten an
"Tapestry users" <users@tapestry.apache.org>
An
"Tapestry users" <users@tapestry.apache.org>
Kopie
Thema
Re: T5: using DOJO?
2007/9/4, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
在 Mon, 03 Sep 2007 16:08:34 +0800，Angelo Chen
<[EMAIL PROTECTED]> 写道:
Hi Erik,
That's good news, I read somewhere that It might be Proptotype not
Dojo.
jQuery will be great, IMO.
+1 for jQuery and http://interface.eyecon.ro
--
( /' _/_ __ _ _
|/|///)(/(/(//_(-/
_/
E-mail: [EMAIL PROTECTED]
Website: http://www.windgazer.nl
"The trouble with doing something right the first time, is nobody
appreciates how difficult it was."
-- Unknown Artist
