-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
