I would suggest breaking the 60 fields over multiple tables (the way you want forms to look like) and link them using references. It will be much easier to handle it long term.
Massimo On May 5, 12:02 pm, JohnMc <maruadventu...@gmail.com> wrote: > Working on another application. One table in the DAL will have about > 60 Fields in it. Using one long form would work but gets rather bland. > I would prefer to visually cut it up. I could either capture the data > in multiple screens for input or use a tabbed interface to capture the > data. I am leaning toward the tabbed interface. > > The one approach I have considered for a tabbed approach is -- > > Controller: > > Build the form using helper functions and pass as to dict() > > View : > > Set up the tabs, display the form and use jQuery hide(), show() > functions using onclick actions to display pieces of the form as > required. > > I would be interested if there might be a better technique to consider > to achieve the same ends. > > Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
