True, I guess you could create your own form superclass that does the default behavior you want.
On 1/27/08, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > also -1. it is trivial to do it yourself automatically like you said > in your blog. there are plenty of usecases that wont work out of the > box. take a common usecase where the label turns red if the field is > in error, how do you do that out of the box? > > -igor > > > On Jan 27, 2008 8:39 AM, Ryan Sonnek <[EMAIL PROTECTED]> wrote: > > Seriously? there are companies that mandate you can't use javascript? > > Even if it's done for you and just works? > > > > Wow...that's sad, but I hardly think that's the norm and such extremes > > should not mandate system defaults. > > > > Any other arguments against such a default? The reason I'm bringing > > this up is that Tapestry ships with client side validation turned on > > by default, and I *really* like using Wicket's Ajax for form > > validation. > > > > Hey...if tapestry can do it... =) > > > > > > On Jan 27, 2008 10:17 AM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > > -1. There are enough companies and projects that can't use or aren't > > > allowed > > > to use JavaScript, which also precludes the default enabling of such > > > functionality. > > > Martijn > > > > > > > > > On 1/27/08, Ryan Sonnek <[EMAIL PROTECTED]> wrote: > > > > > > > > out of curiosity, would there be any interest in shipping Wicket with > > > > Ajax form validation turned on *by default* instead of developers > > > > manually adding the AjaxFormValidatingBehavior? Are there any > > > > drawbacks to having this be the default behavior? > > > > > > > > On Jan 27, 2008 9:00 AM, Ryan Sonnek <[EMAIL PROTECTED]> wrote: > > > > > http://www.jroller.com/wireframe/entry/wicket_client_side_validation > > > > > > > > > > I've spent the past couple weeks investigating Wicket's support for > > > > > client side validation. IMO, using Ajax for validation in Wicket is > > > > > really amazing. Lots of folks are touting "javascript validation" > > > > > right now, but I think Wicket has a definite advantage because the > > > > > Ajax validation *reuses* all of your server side validation for free! > > > > > This might be worth mentioning on the feature list somewhere and I'd > > > > > be interested in any comments. > > > > > > > > > > Ryan > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > -- > > > Buy Wicket in Action: http://manning.com/dashorst > > > Apache Wicket 1.3.0 is released > > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 > > > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
