Lee Bolding wrote: > Speed isn't really a concern - I'm more concerned with readability, > maintainability and extensibility. Besides which, the page gets built once, > then cached - so your point is moot.
It's a moot point for you - not everyone caches, and I don't think the use of unneeded function calls to make templates look nicer should be encouraged. > If we continue your endform_tag logic, why bother with the other asset > helpers? > I see far more use for this than say the stylesheet or javascript helpers, > which essentially don't do anything else other than prefix /web/css and > web/js respectively. They are there, in my opinion, to make it easier to roll out static content servers - if your website grows to the point where you want to move static content (css,images,js) onto it's own server - then if you've used the helpers for thse things, you have a single point to apply the change. This logic doesn't follow for links. Most other helpers require logic, the javascript ones automaticaly include javascript, and do route translations for example. > The point of the helper is to make life easier by outputting valid xhtml - > with </form> you can't get this wrong - where you can specify multiple > options, you can. If you want a link helper for normal links, you can of course create your own - however I don't think symfony should provide one - the line has to be drawn somewhere with what functions are included in helpers, and in my opinion the lack of helper to print out a simple href does make sense. Of course - should you wish to create your own, you'd want to use the content_tag() helper function --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
