Fallback? That should always be done fallback or not, clientside is jus a quicker feedback to the user, the real validation should always be done after that on the serverside
On 6/26/08, Matthijs Wensveen <[EMAIL PROTECTED]> wrote: > I know ASP.Net has this too, and falls back to the server when client > side validation is not possible (or is hacked by a smarter than average > user). Something could be done. I think would be worth the time when you > have it (time, that is). I'd start with a separate project, so that > people can try it out. > > Matthijs > > Manuel Corrales wrote: >> Hi, i dont want to be flamed by this post, i have read on some places some >> not very polite things about wicket vs taperstry. I think that all >> frameworks have pro and cons. Here is the thing, i was using Tapestry 5 >> for >> a while, and now i am developing with wicket. One thing i liked about T5 >> was >> the "magic" on the client side validation without the need to write >> javascript, and it worked pretty good. I really do not have the time now, >> but it would be great to accomplish something like this: >> >> RequiredTextField tf = new.... >> tf.enableClientSideValidation(); >> >> my approach would be to borrow the T5 code to generate the required >> javascript. >> >> Is this idea worth the time? >> >> Best regards. >> >> Manuel. >> >> > > > -- > Matthijs Wensveen > Func. Internet Integration > W http://www.func.nl > T +31 20 4230000 > F +31 20 4223500 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Sent from Gmail for mobile | mobile.google.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
