I'm thinking that is probably where things are going to need to go eventually. The only issue is that without "some" kind of library all of the built in Tapestry javascript becomes unreasonably unweildy if forced to do a lot of things from scratch.
It's possible that something like dean edward's( http://dean.edwards.name/weblog/) Base2(http://code.google.com/p/base2/) implementation could be used as the Tapestry core js library while allowing for different libraries to be "plugged in" somehow so that everyone can use the library of their choice and not have one forced on them. (well, besides the Base2 - something has to be used so it's just a matter of how large/functional enough it is for tapestrys needs while not being too large to be included along with whatever other libraries people want) This can get a little tricky in various places but it does seem clear that this will need to be addressed eventually in order to make as many people happy as possible. (since js library choices can often be a very personal choice it's not likely that one will ever suite all needs) On 7/14/07, Bill Holloway <[EMAIL PROTECTED]> wrote: <snipped>
Actually, how about an abstraction library in T5 so that we could plug in any javascript library we like for Tapestry components? bill
</snipped> -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
