I'm really ok with "whatever", just so long as people don't want us to maintain our own javascript library implementations.. The current setup has the potential to already provide enough abstraction to swap out and use whichever javascript library people would prefer.
As for the size of the build, this can certainly be adjusted and I think I will have to do that at least. Including / not including javascript on a page at all depending on usage is probably just one of those 20% rule kind of things. I've been waiting to see what real world usage would produce, and this feedback is invaluable for that. It won't be easy but perhaps it is coming close to the point were optionally including it becomes more of a priority. I'm still going to be out of contact for normal Tapestry stuff for the rest of the week while I finish up this ognl compilation stuff but should be back to normal after that. <snipped> -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
