Just to clarify your answer....

with form = SQLFORM(...) then {{=form}} serializes in HTML but the 
corresponding objects exist even if you don't.
with form = JForm then {{=form}} only makes a <div/> which JS (provided) 
converts to a form. There is no server-side DOM and this make it a lot 
faster.

On Saturday, 6 September 2014 20:27:28 UTC-5, Anthony wrote:
>
> On Saturday, September 6, 2014 5:30:44 PM UTC-4, Ide wrote:
>>
>> I like the idea of a slimmed down equivalent of SQLFORM. However, I think 
>> it should be written to permit client side rendering via js scripts, or 
>> server side rendering in views; as such the output as json or python 
>> object/array would be ideal.
>>
>
> I don't think we necessarily want the framework itself to have to support 
> server side rendering -- that would involve a lot of code duplication. 
> However, you could easily use the metadata output in your own code to 
> generate the HTML, or just continue to use the existing SQLFORM.
>  
>
>> Personally I prefer python to javascript so would render server side 
>> myself.
>>
>
> Keep in mind that with the new system, you won't necessarily have to write 
> Javascript -- the Javascript that renders the forms will be provided by the 
> framework.
>  
>
>> I do think SQLFORM offers useful features but I sometimes end up 
>> discarding all the generated html to use my own custom view, which means 
>> wasted processing time on the server.
>>
>
> Note, if you don't do {{=form}} in the view, then the form is never 
> serialized into HTML (though the server-side DOM is created, so there is 
> still some waste if you're not using any of the HTML or widgets).
>  
> Anthony
>

-- 
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.

Reply via email to