Bill,

Not to strain the point, but why complicate matters with DD/DT lists
to accomplish this? 95% of your example can be delivered with a
standard SQLFORM. Store the result in a var, serialize it with xml()
then tweak it with python code if you need, the balance by some
changes in CSS classes.

Take a look at the CSS in your example. They have heavily modified the
definition structure to be more inline. Far from the std 2 paragraph
style with the sibling '<dd>' indent. SQLFORM already provides for a
defined inline style with both <label> and form elements properly
annotated with id's and classes. High learning curve with SQLFORM but
its worth the effort.


On Jun 15, 2:04 pm, Bill <isp...@gmail.com> wrote:
> Massimo,
>
> Need clarification.  Not certain of the best approach.
>
> Some questions(1-5):
>
> 1. How do you overide exposed URLs for register (def register), login
> (def login) etc. ?
> 2. Do you use conditional statements inside of def user?
>
> The example below represents your previous answer inserted inside
> function user.  3.  Is this the right way to go?
>
> def user():
>
> {{=form.custom.begin}}
> {{=form.custom.widget.somefield}}
> ...
> {{=form.custom.submit}}
> {{=form.custom.end}}
>
> return dict(form = auth())
>
> Reference:
>
> http://www.web2py.com/examples/default/tools
>
> def user():
>     return dict(form = auth())
>
> The above action will expose the following URLs
>
>     *http://locahost:8000/application/default/user/register
>     *http://locahost:8000/application/default/user/login
>     *http://locahost:8000/application/default/user/logout
>     *http://locahost:8000/application/default/user/verify_email
>     *http://locahost:8000/application/default/user/profile
>     *http://locahost:8000/application/default/user/change_password
>     *http://locahost:8000/application/default/user/retrieve_password
>     *http://locahost:8000/application/default/user/groups
>
> 4. Is this how you would handle DT terms? How do you incorporate
> input, dropdowns, and checkboxes/radio buttons?
>
> table=TAG.DL(TAG.LEGEND('List header'),
>   DT('Term1'),TAG.DD('This is the definition of the first term.'),
>   DT('Term2'),TAG.DD('This is the definition of the second term.')
>   )
>
> {{=table}}
>
> Would like to be able to create custom forms using definition lists.
> The link below has all the elements placed.  It looks like where I
> need to go.  5. Your thoughts?
>
> Reference:http://www.andrewsellick.com/examples/accessible-form/
>
> Thanks, Bill
>
> On Jun 15, 11:33 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > You can already do this:
>
> > table=TAG.DL(
> >   TAG.TH('List header'),
> >   TD('Term1'),TAG.DD('This is the definition of the first term.'),
> >   TD('Term2'),TAG.DD('This is the definition of the second term.')
> >   )
>
> > {{=table}}
>
> > On Jun 15, 12:28 pm, JohnMc <maruadventu...@gmail.com> wrote:
>
> > > Definition lists. Its a variant of the LI/UL construct. Example --
>
> > > <DL>
> > > <LH>List Header</LH>
> > > <DT>Term 1</dt><dd>This is the definition of the first term.</dd>
> > > <DT>Term 2</dt><dd>This is the definition of the second term.</dd>
> > > </DL>
>
> > > You see it most often used in blogging and occasionally for book
> > > indexes.
>
> > > On Jun 15, 11:04 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > > > 1.  Is there any plan to have support for definition list?
>
> > > > what are they? can you provide an example of what you have in mind?
>
> > > > > 2.  How do you incorporate custom forms with Auth?
>
> > > > yes, you can build views for forms that look like this and insert any
> > > > html you like:
>
> > > > {{=form.custom.begin}}
> > > > {{=form.custom.widget.somefield}}
> > > > ...
> > > > {{=form.custom.submit}}
> > > > {{=form.custom.end}}
>
> > > > (requires latest trunk)
>
> > > > > 3.  Is that possible?  If not, do you use "if form.vars
> > > > > accepts"  (Syntax ?)
>
> > > > yes.
>
> > > > > Thanks,
> > > > > Bill
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to