> One obvious advantage of having ajaxified client-side validation is that the > server-side validation and client-side validation will look exactly the > same!
Ajax isn't the answer for this problem. You don't have to go to the server to get consistent error reporting, adding and removing elements from the t:errors div using good old DHTML isn't complicated, and would make a nice alternative to the bubbles. The client side error handling should definitely provide extension points so these options can be added. On a side but related note: I'd also like to be able to pull the t:errors out of the form and allow multiple forms to post to the same error area at the top of the page... Josh On Thu, May 15, 2008 at 5:03 AM, babbler <[EMAIL PROTECTED]> wrote: > One obvious advantage of having ajaxified client-side validation is that the > server-side validation and client-side validation will look exactly the > same! > > ----- Original Message ----- From: "babbler" <[EMAIL PROTECTED]> > To: <users@tapestry.apache.org> > Sent: Thursday, May 15, 2008 5:08 AM > Subject: [ANN]: T5 website and validation feedback > > >> I've been working on a T5 and Flash based website - building a version of >> the good old acrophobia game. You can check it out at www.acrobabble.com. T5 >> is shaping up to be a great framework. However, I do have some feedback on >> the form validation mechanism. As you can see from the acrobabble website, >> if you just tab through the login fields, you get broken error messages >> because of the div being too small where the blurbs are created. The >> framework will never be able to properly guess where the blurb should be >> inserted and as a consequence wrapped blurbs like I'm getting are >> inevitable. >> >> I really wish T5 would support validation like is seen on Yahoo mail's >> sign up page. Go to yahoo.com and click on Sign Up for mail. The fields seem >> to have various "tags" associated with them: >> >> - Displayed when the field gets the focus >> - Displayed when the field loses focus and validation occurs. >> >> I saw a few emails that referred to validation using onBlur. I think every >> field should be able to drive certain events: >> >> onFocus: This should allow you to specify one or more components (say by >> Annotation in the getter for the field) that should either have their css >> changed or be ajax-updated when the field gets focus. >> onBlur: Fire validations and allow the developer to specify in which html >> tag (div or span, etc.) the output of the validation should be displayed and >> optionally additional components that could have their css class changed. >> >> This will make for an extremely powerful and flexible validation framework >> and will get us away from the blurbs (which can be very annoying to use as >> they cover up the field). My humble opinion is that the above change is a >> necessity given the other superlatives that T5 boasts (hint: Howard - appeal >> to ego! :) >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -- TheDailyTube.com. Sign up and get the best new videos on the internet delivered fresh to your inbox. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
