Tapestry's stronghold is the server side. What I really like to see is a well defined structure and JavaScript API so that we can use it to enhance the client dynamics by handcrafted javascript or by integrating other Ajax tools. For example, I can not find any document on how to customize the client site validation and/or how the client side validation works. I see that the client side validation all happen at the form submit time. I have to read the source code to figure out how it works. And my investigation showed that I can not use Tapestry's validation scheme to validate fields when it loses focus, also I can not perform a form level cross-field validation before submit. Then, my final decision is: do not use any Tapestry client side validation, I hook up my own javascripts by element ids.
To incorporate my view, I imagine the following features will help alot: 1. Render the component type to the page. For example, when render DatePicker, add a attribute tapType="DatePicker". 2. A javascript to operate on the components, for example, tapestry.datepicker.enable(comp), tapestry.datepicker.setDate; tapestry.datepicker.hide(), tapestry.datepicker.setIcon,... Thanks. Best Regards, On 2/10/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > 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. > > > > > >
