One of the returning moments on this list is that when I say helpers
in controllers, people hear 'html in code'. The two have (almost)
nothing in common, even though it's possible to overuse/abuse helpers
(just as you can put html in strings in controllers - obviously bad).
Then again, maybe it's just me having an awkward POV on helpers :)

My main question is - why do people consider transferring only stock
variable/list/dictionary python objects to the views 'cleaner' than
transferring any other python object to it (helper objects, or even
your own) ? Helpers create *objects* which are just data wrappers.
They are *NOT* strings and have nothing in common with HTML until the
point they get rendered.

On Feb 18, 12:03 am, carlo <[email protected]> wrote:
> On 17 Feb, 23:39, AchipA <[email protected]> wrote:
>
> > web2py gives quite some latitude with regard to doing things... I
> > understand there are major no-nos, but is there a best way ? We had
>
> Sorry but I would be more narrow minded about this: from my point
> there *should* be never a good reason to put html in controllers: it
> makes code difficult to debug, to read and to share with designers.
> Isn't this one of the reasons for php and java servlets failure in the
> enterprise?
>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to