That seems reasonable enough, but I'm not sure I understand your meaning in relation to adding more scripting support.
Have you seen the @Script component (which the DatePicker uses) ? I don't think I've seen a web framework that provides more scripting support than tapestry. Regardless, I would definitely anticipate the DatePicker render logic to change somewhat in tapestry 4.1, as tapestry will fully support most ajax functionality that can be thought of by then. jesse On 2/10/06, Cliff Zhao <[EMAIL PROTECTED]> wrote: > > We had a problem of disabling DatePicker field in javascript. Although the > input can be disabled, the calendar link can not. That gives some weird > feeling. We finally make it disabled with JavaScript, but it may not be > future-proof. It may not work if Tapestry changes how the DatePicker > renders. > > I think that Tapestry do not need to be a fully ajax capable framework, > but > I think Tapestry should be ajax friendly. I mean that Tapestry pages > should > be easily enhanced by javascript. > > Just my two cents. > >
