tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Sommerville" <...@bulletproof.com.au>
Subject RE: RE: Prototype vs. JQuery vs. Dojo 0.9 vs. ???
Date Thu, 04 Oct 2007 00:36:34 GMT
No, I wasn't going that far.  

More that the core library would never directly generate
javascript, but instead call a pluggable interface for the
required functionality.  The module that implemented that
interface would then output the required javascript

I would see those interfaces as "intention" driven rather
than functional driven.  That is they would be based on
the task the core is trying to accomplish rather than 
the features/functions of available javascript libraries.

Its all very fuzzy at the moment & I think it would need 
a bit of trial & error to get right.


> -----Original Message-----
> From: Julien HENRY [mailto:henryju@yahoo.fr] 
> Sent: Wednesday, 3 October 2007 10:03 PM
> To: Tapestry development
> Subject: RE : RE: Prototype vs. JQuery vs. Dojo 0.9 vs. ???
> @Ben: Do you think about something like GWT? I mean
> programming JavaScript in Java.
> Components (especially AJAX ones) will certainly use
> various existing JavaScript libraries. I think the
> main issue is "what about T5 core components?". Should
> they use a specific library (without preventing
> additional components for using their own)?
> Don't know what could be the best solution... sorry.

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

View raw message