> Also, something that still confuses me is what is best practice for where to > put view code. When is it best to rewrite tag defs in application.dryml, > when is it best to extend them in views, and when is it best to use them with > parameters in views? These could just be where I had trouble though - hard > to say if other people would have completely different issues.
Theoretically I go by the dry principle: if it's used more than one place then it belongs as an extended tag if it's one time only, it can go as a page override Realistically I go by the laziness principle: put it wherever it's less work overall For a counter example to the first principle, sometimes you have a handful of pages that don't need a particular element of the standard page. It's easier to override each page and tack on an without- parameter-name on those handful of pages than it is to make an alternative page that removes that parameter. -- You received this message because you are subscribed to the Google Groups "Hobo 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/hobousers?hl=en.
