clientValidationEnabled still means ~almost~ the same thing on the Form component, only it has less to do with whether or not a particular .js file is loaded as I'm letting dojo do that for me now..
This is something I've been avoiding thinking about until things stabilize a little more, but the overall feeling is that I like the freedom/cleanness of the client side API when not having to worry about doing .js includes for dojo / other things. It's not something that won't be addressed, just haven't done it yet. The good news is that the Asset service has had some rather important fixes made to it so that most assets will be properly cached now. (Also handles url () references embedded within stylesheets/ lots of other goodies.) I plan on writing a few profiling unit tests to get a definitive measurement of the impact on including/not including dojo by default to be sure no one is guessing. Having to manage including/not including dojo on an individual basis will add a lot of API overhead/burden that I'd rather not go through unless it is a real issue. I also haven't built a proper compressed profile build yet, which I hope will be the absolute minimum profile size possible...It won't matter if it includes only a tiny fraction of dojo as anything that is really needed at runtime will still be loaded/cached on an as-needed basis. On 6/28/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
On Wed, 28 Jun 2006 12:38:20 -0400, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > Yeah, "oops". I should probably refactor that @Shell inclusion part to > have > dojo included by default, and let people opt-in for ajax-specific > functionality on a per page/component basis. Yeah, the current way seems broken to me. Is clientValidationEnabled still a valid option for the Form component? If so, then it would probably make sense for either that or the Shell parameter to be the catalyst for loading up dojo. I wouldn't want to send dojo out on every page request if it's not being used in all places. > Dojo is included within the tapestry jar, so you shouldn't have to go > through very much to use it now. (unless you want to override the version > included, which is also supported. ) Good to know. -- Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
