These are convenience classes, and can be useful when generating page
elements with code (you don't have to worry about balanced HTML elements,
nesting, etc. so much then).
Sometimes, things are more readable when you use the helpers to place
elements in the middle of template code (so it is a readability / stylistic
choice then), e.g.:
{{ for item in list:
TD(TR(item))
}}
just might look better than the alternative
On Wed, Jul 22, 2009 at 3:31 PM, Julio <[email protected]> wrote:
>
> This has came up countless of times, you'll find many supporters, mid-
> grounds and opposers I believe html helpers have their place in web2py
> and are good for say, prototyping and stuff, but the bottom line is
> that you *can* create entire web2py apps without using them at all, as
> in my case.
>
> hth,
>
> -- Julio
>
> On Jul 22, 9:41 am, gillengam <[email protected]> wrote:
> > Excuse me for my question. I'm not sure that it is good use HTML
> > helpers. They are very powerful, but I'm afraid that they are no good
> > for MVC architecture. I've seen that all framework use them, but I'm
> > not sure that it's a good idea. I think to an HTML designer that don't
> > know programming. I know that HTML helpers aren't required, but then I
> > ask me which is their benefit in big projects (with programmers,
> > designers, ...). I'd like to understand this. Can you help me?
> >
> > Thanks
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" 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
-~----------~----~----~----~------~----~------~--~---
