I wanted to make the point on one of my favourite subjects, forms designed in the best MVC pattern possible, so I browsed the forum searching for the latest achievements to this respect. I found different solutions but they looked a bit more like extemporaneous tricks than a reference "how to". I found to different degrees: Bill's Patch, DenesL custom forms, rfx_labs custom forms (where you can find the underdocumented "form.element" syntax) and forms "the Tim Farrel" way.
I can not understand why in the documents/tutorial/examples forms are always designed in a usual "everything in the controller" pattern: saying "always" maybe I am exaggerating a little, but this is the trend. I find this a bit uneducating because it brings to coding controllers just the worst php manner. I would prefer there was a "suggested" web2py way used throughout every example. My "good " forms, at least: - data queries in controller or model - define a "form" object in controller is acceptable - helpers and/or html in views - validation facilities must be preserved - forms auto submitting must be preserved May I ask someone to summerize, as 1.56.3 version is out, the best/ suggested way to design forms following an MVC pattern as clean as possibile? Thank you carlo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
