Great idea!
I think definitely web2py should be optimized towards ajax and javascript.
I do not use SQLFORM because fixing the html it generates often takes more
time than to write my own html. I think there are some improvements that
can be done to forms anyway, which can be implemented in a new standard.For
example that it's a bit tricky to remove colons from form labels.
Also, I suppose this change will affect auth.login() et.c. too? It would
just be so much better to have ajax alternatives here.
Furthermore, if I want to edit the form action attribute (as I cannot just
do *form['_action'] = myvalue*), and a more straight forward way to deal
with "remember me" (as there is no *form.custom.rememberme*).
To standardise these issues web2py style would really improve the
framework, imho.
Thanks again for a great framework!
Den fredagen den 5:e september 2014 kl. 07:56:23 UTC+2 skrev Massimo Di
Pierro:
>
> Please find attached a welcome4.zip with contains the following files:
>
> controllers/default.py
> views/layout.html
> vides/default/index.html
> modules/jform.py
> static/js/jform.js
> static/js/jform-bootstrap2.js
> static/js/jform-bootstrap3.js
>
> My proposal is the following:
> 1) deprecate SQLFORM (but keep it for backward compatibility)
> 2) replace
>
> form = SQLFORM(table).process()
> ...
> {{=form}}
>
> with
>
> form = JForm(table)
> ...
> {{=form}}
>
> what is the difference? SQLFORM generates html. JForm generates JSON
> metadata which is then converted into the form client-side by the js in
> jform.js.
> why?
> - it is much faster because all rendering is done client-side
> - it can "optionally" submit the form via Ajax without having to change
> your code.
> - it is much easier to style and create widgets for different css
> frameworks.
> For example include the right one:
> static/js/jform-bootstrap2.js
> static/js/jform-bootstrap3.js (I only provide a layout for bs2 and not bs3)
> - it is much more powerful because you can customize widgets in JS.
>
> We could also add a JTable, a JMenu and a JLogin and keep all the styling
> info in JS files as opposed to Python files.
> This would make web2py leaner and cleaner.
>
> Thoughts?
>
> Massimo
>
>
>
>
>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
