> a plugin comprise of a set of components (modules, models, views, > controllers and static files) that may be used by more than one app > and act on the global variables (request, response, db, etc.) of the > app that uses the plugin. Examples are CRUD and authentication.
thank you. > > Reading the T2 manual I also found "It used to be common to create a > > <form>...</form> that submits the form variables to a different > > page. This is no longer considered good practice." > > This reopened an old argue I have with web2py validation because if > > you want to benefit of the accepts() feature you must put some form > > presentation/helpers in the controller. > Did you look into gluon.sqlhtml.form_factory() which is described in > the book? mmh..which book please? > > Is the Tim Farrell solution as in the "Customizing Forms" thread still > > the best? Or something new was added to the web2py cookbook in this > > respect? > I think that solves a different problem, inserting hidden fields > (_formkey and _formname) in custom forms. Am I wrong? no it exactly addressed this great (imho) problem, in Tim's words: "I crossed this bridge a few weeks ago. I, like you, don't dig the whole presentation logic in the controller. However, it is still reasonable to build a "form" in the controller for logical data-handling purposes. " --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
