Just to get some resolution on this, are there any definitive yes/no thoughts on whether or not tapestry should include any form of dojo? I've received confirmation that the license is compatible with apache's, so it should be ok in that respect.
If any was included I'd think it would be very very minimal in footprint as I'm sure the majority of it won't be used directly, at least not initially. I would however like to eventually re-factor some of the javascript (ok, maybe more or less all) in tapestry to work off of more of the dojo ant build scripts so that we can start adding js unit tests and build packaging to provide an easier to navigate source structure/overall stability. I'm sure the ajax stuff could probably be left open for debate, but I'm still leaning initially towards being able to provide very direct support/implementation for it within tapestry, leaving tacos to focus on writing really cool components. (Not that tapestrys components won't be re-worked, we'll have to define which tacos components get included and which don't I guess ) The recent asset changes sort of make the inclusions possible now, but I think the Shell component/global asset inclusion logic needs to be completed before anything like this can begin. Thoughts? jesse
