--
-- mail from:GoogleGroups "web2py-developers" mailing list
make speech: web2py-d...@googlegroups.com
unsubscribe: web2py-develop...@googlegroups.com
details : http://groups.google.com/group/web2py-developers
the project: http://code.google.com/p/web2py/
official : http://www.web2py.com/
---
You received this message because you are subscribed to the Google Groups "web2py-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py-develop...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
form.py and web3py are separate things. form.py is a just a better sqlform with sligtly different apis. It will work on both web2py and web3py (when we figure out what it is). form.py uses the same serverside validators and the same clientside validators we have now but I am creating a whole new set of client side widgets that I think should replace the current ones http://mdipierro.github.io/stupid.css/widgets/index.html (they do not require stupid.css). The do partial client-side validation.
--
Also take note that, whether we provide javascript validators or not. I'm not sure if we should myself as I think that's best left to whatever javascript library the users like to use or even to widget plugins. The form's input, any input really, will still need to be validated server side. input that is not validated is the root of all evil.These validators are also pretty much independent of what you choose to make the form with. The DAL will call them himself if you use methods like validate_and_insert.