On Feb 18, 7:43 pm, carlo <[email protected]> wrote: > Working in team they are almost useless: the html code is usually the > source for your logic not a "product" to pass designers. You get html > static pages with style and putting in some logic is your business.
I guess I'm just terrible at expressing myself. There is no uncrossable difference between helpers and plain lists/dicts, and thus there doesn't need to be any appreciable difference in templates using one over the other, either. On the other hand, while the designers are sleeping, the coder CAN use the helper's native output to speed up prototyping and ensure standards compliance. Sometimes I even use two separate views for the same controller function - one from the 'designer' and one for development. The helpers in this sense make it actually easier to work in teams. As the controller output is the same, I can mess with my functionality/ debugging oriented views, while not breaking the 'simple', element oriented view supplied by the designer. To reiterate - the way I see it helpers are objects just like lists or dicts and can thus be used in the same way with regard to controllers or views. If you do not get carried away, you only gain additional functionality compared to the case you skipped using helpers altogether and thus it cannot 'worsen' MVC compatibility or teamwork than what the basic MVC model already requires/allows for. To all who I have not convinced and/or have wasted their time to read my lengthy posts about this arguably philosophical point - sorry, I'm over and out :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
