tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From andyhot <andy...@di.uoa.gr>
Subject Re: Prototype vs. JQuery vs. Dojo 0.9 vs. ???
Date Wed, 03 Oct 2007 01:46:29 GMT
In my mind there's only one correct answer for Tapestry to this:
nothing and everything!

ext is looking great these days, yui is ... yahoo, dojo 0.9-1.0 is sooo 
and prototype is ... the good old prototype - and who knows what's to come

If anyone's been looking at my recent 4.1 commits, i've set to abstract 
all dojo calls through
the tapestry object - and i've been able to do this by introducing just 
6-7 more functions in it.
And i can now replace dojo with other libraries - i expect a few more 
technical challenges, but
it should be straightforward to work

So, perhaps this would prove as a guide for T5 as well

Howard Lewis Ship wrote:
> I've been having some fun wrapping my brain around JQuery.
> I'm not fully certain its a great fit however.
> For hand-tooled web pages, maybe traditional JSPs, it would be perfectly
> good.
> But it's really built around identifying elements that need "special
> attention" in terms of CSS class and page structure, and then applying
> uniform effects and logic (in the form of even handlers) to them.
> Tapestry is more geared towards the server side "seeding" the client side
> with specific element ids, and then hooking up the appropriate event handler
> that way.
> In fact, that is more Protoype's angle, the whole point of $("myid") being
> so easy.  JQuery lets you use Document.getElementById() ... it's one area
> where the $() function has no great magic.
> Can Tapestry shift?  Should it?  Would the newly revised Dojo be a better
> fit?

Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / JEE Consulting

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message