I'd love to use it, but the ValidDatePicker on tassel appears to be
GPL'd, not LGPL'd so I can't use the thing unfortunately (some degree of
source confidentiality is part and parcel for what I do). LGPL I'm peachy
with, but I can't expose the whole app's source.
Thanks anyway,
--- Pat
> -----Original Message-----
> From: Pablo Ruggia [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 15, 2005 1:12 PM
> To: Tapestry users
> Subject: Re: Validating a DatePicker
>
> There is already one ValidDatePicker (don't remember where). It's already
> a
> mix between validfield and datepicker. But it's behaviour is the same, if
> user enters a bad formatted date, it will transform it to null.
> I think you can download ValidDatePicker and then edit this to generate a
> validation error when the format is bad.
>
> On 8/15/05, Patrick Casey <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > When the datepicker widget draws, you get an edit box, and a
> > button to click that pops up a calendar widget. You can either set the
> > date
> > via the widget, or you can just write in any old date you want to via
> the
> > text box. The question becomes though, what happens if the user types in
> > an
> > invalid date e.g. "Patrick" instead of "12/25/99"?
> >
> >
> >
> > The behavior *seems* to be to return null to the bound
> > component, which really isn't going to get the job done for me because I
> > need to be able to differentiate between "user didn't choose a date" and
> > "user put something in the date box, but it's nonsense".
> >
> >
> >
> > Is there a way for me to validate the string in the datepicker's
> > box before the internal datepicker logic decides to null it out? Or am I
> > going to have to scrap the datepicker and just roll out a ValidField and
> a
> > DateValidator?
> >
> >
> >
> > --- Path
> >
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
