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.
If we continue your endform_tag logic, why bother with the other asset helpers? An endform_tag would literally output "</form>", which is more characters (although I think it's actually easier to understand than a mismatched form_tag and </form> pair [how many editors barf at this???], but I digress...) whereas my proposed tag would have options such as target, class, id, style etc. 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. 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. :) -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Ian P. Christian Sent: 06 December 2007 14:31 To: [email protected] Subject: [symfony-users] Re: Asset helper for "generic link"? Lee Bolding wrote: > Is there some solution that I'm missing other than manually coding the link > in my template? (which looks a bit odd when mixed amongst all the link_to's) It might look odd - but it's faster.... I don't really see much point in implementing a function just to make things look nicer in the template, that's like asking for a endform_tag() function, just because there's a form_tag() isn't it? -- Ian P. Christian ~ http://pookey.co.uk --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
