@Łukasz : Thanks a lot for the response. But as Henrique mentioned using
the __init__()in the view class and then returning a JSON response would be
server side right ? Or Am i missing something here ?
I was thinking something on the lines of this. Add an
attribute in django.forms.fields which will include the js media having the
client side validation ?
On 4 February 2012 04:47, Henrique Bastos <[email protected]> wrote:
> Django's form could use a more high level solution for both client side
> form validation and asynchronous form validation.
>
> Djaxproject.com is ok, but is too ad hoc. It would be nice to have
> Adrian's and Łukasz perspectives combined somehow.
>
> []'s,
> --
> Henrique Bastos
> +55 21 9618-6180
> http://henriquebastos.net
> http://twitter.com/henriquebastos
>
> On 03/02/2012, at 19:57, Łukasz Rekucki <[email protected]> wrote:
>
> > On 3 February 2012 22:03, Adrian Holovaty <[email protected]> wrote:
> >> On Fri, Feb 3, 2012 at 11:46 AM, Karthik Abinav
> >> <[email protected]> wrote:
> >>> I was thinking about a feature that could be implemented. For common
> >>> fields like username having only alphanumeric , or phone numbers
> having only
> >>> numbers, a client side validation need not be written every
> time.Instead one
> >>> could directly write something like,
> >>>
> >>> forms.CharField(validator = "usernamevalidation")
> >>>
> >>> in the forms definition and the client side validation for that field
> would
> >>> automatically be taken care of by the validator class. This will save
> a lot
> >>> of time while making large websites with lot of registration forms and
> in
> >>> general be helpful to people who dont really know javascript and yet
> want
> >>> some amount of frontend validation in place.
> >>
> >> I like the idea of having a JavaScript version of form validation.
> >> Basically we could make a view class that takes a Form object in
> >> __init__() and returns JSON of the errors in a consistent way -- this
> >> would be very easy to do. Then we could provide some standard
> >> JavaScript to parse that JSON and add the error messages to the
> >> appropriate fields in the form in a consistent way.
> >
> > I don't get it. That would require sending the data to the server
> > (right?), so it's not
> > really client-side. I think http://www.dajaxproject.com/ does exactly
> that.
> >
> > What I would like to see instead is providing HTML5 attributes for
> > standard fields and
> > making it easier to add ones to custom ones. Some simple to implement
> > ones are: "required", min/max for number fields, max_length for a
> > textarea. Regular expression can be supported via "pattern" (with some
> > code to translate them to JS regexp syntax).
> >
> > --
> > Łukasz Rekucki
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Django developers" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> [email protected].
> > For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>
Regards,
Karthik Abinav,
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
