This behaves in a somewhat similar manner and as far as I have gone through
this and tested, I am pretty happy with this. But I would still prefer
having some HTML5 attributes with fallback javascript as well. Since these
new html5 features are becoming more and more popular among the web
developer
On 7 February 2012 10:01, Tai Lee wrote:
> I found that Alex's `django-ajax-validation` works pretty well for
> this and I think it works the way you described. Perhaps it could be
> updated and included into Django core, if there is good support for
> it.
>
> https://github.com/alex/django-ajax-
The problem I've run into with client-side validation of django
projects is:
1) If you can't replicate every piece of validation the server does,
the user experience will be inconsistent, which is bad.
2) You can't replicate every piece of validation the server does.
Simple example: uniqueness che
I found that Alex's `django-ajax-validation` works pretty well for
this and I think it works the way you described. Perhaps it could be
updated and included into Django core, if there is good support for
it.
https://github.com/alex/django-ajax-validation/
Cheers.
Tai.
On Feb 4, 8:03 am, Adrian
@Ł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.
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://henriq
On 3 February 2012 22:03, Adrian Holovaty wrote:
> On Fri, Feb 3, 2012 at 11:46 AM, Karthik Abinav
> 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 validatio
On Fri, Feb 3, 2012 at 11:46 AM, Karthik Abinav
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 dire
Hi,
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 = "us
