Currently SQLFORM renders a complete table for the fields provided (or
all) for a db.table, and does some other magic as well.
Would love to reuse the magic, but be in more control of the
rendering. Eg, would like to specify what fields are placed where, and
if they should include labels or not etc.
What fields are to be rendered where should be easiliy done form the template.
(the underlying table is quite big, and when all is listed like it is
now it's too overwhelming. A different layout makes it far more better
(esp when throwing in some ajax), eg having some sort of matrix,
having some labels only for rows and columns vs for every field)
Any suggestions?
I'm digging in the code, and find that the fields and the rendering of
the fields are glued together and not easy to seperate/re-use. Might
be that I'm missing something here.
Would like to do something like:
{{=form.start}}
<table>
<th><td></td><td>header 1</td><td>header 2</td><td>header 3</td></tr>
<tr><td>{{=form.field['field1'].label</td><td>{{=form.field['field1']</td><td>{{=form.field['field2']</td><td>{{=form.field['field5']</td></tr>
</table>
<div>
<span>{{=form.field['field3'].label}}: {{=form.field['field3']}}</span>
</div>
<div>
{{=form.submit}}
</div>
{{=form.end}}
where the fields have the currently shown widgets in place without the
need for me to construct these...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
