Re: [GSoC 2016]Proposal: Validity check at client and dynamic form framework

2016-03-22 Thread Tim Graham
I agree with Jani that you should think about trying to make the proposal accommodate different JavaScript frameworks. You might look at https://github.com/jrief/django-angular, for example, for inspiration. Just thinking about what problems Django should be trying to solve, I'm wondering if cl

Re: [GSoC 2016]Proposal: Validity check at client and dynamic form framework

2016-03-22 Thread Jani Tiainen
On 20.03.2016 14:59, Lover Di wrote: Hi, I have been working for preparing a proposal about a new feature for Django. I'm posting my draft proposal to Gist and want to know my idea is OK or not. So I can proceed with the right approach. Any suggestions or advice are welcome. Abstract of m

Re: [GSoC 2016]Proposal: Validity check at client and dynamic form framework

2016-03-21 Thread Cristiano Coelho
I don't have enough enough knowledge on how GSoC works and what the django team expects from people proposing projects but if it was me I would rather have a very well implemented, tested and with a good level of customization client side validation than two not so well features but that's up to

Re: [GSoC 2016]Proposal: Validity check at client and dynamic form framework

2016-03-20 Thread Cristiano Coelho
The client side validation is a very good idea, other frameworks such as ASP.NET MVC already has some basic client side validation tied to model fields (equivalent to django forms) and also provides a very easy way to add custom javascript validation and tie to the model/form. For the second pa

[GSoC 2016]Proposal: Validity check at client and dynamic form framework

2016-03-20 Thread Lover Di
Hi, I have been working for preparing a proposal about a new feature for Django. I'm posting my draft proposal to Gist and want to know my idea is OK or not. So I can proceed with the right approach. Any suggestions or advice are welcome. Abstract of my proposal: - Automatically generate s