On Nov 5, 2010, at 4:19 PM, Domizio Demichelis wrote: > > That's a good question. Unlike the rest of Rails, there's not really a good > way to "autoload" taglibs, apart from the basic functionality involved in > subsites. It's basically back to the old days where file structure was > arbitrary and glued together with #includes (or in this case <include>s). I'd > be glad to hear any suggestions or even just practices that others on this > list have to manage the mess. > > In the 1.3.* version I implemented a simple autoloading of taglibs (no > <include> needed). > > All the .dryml files dropped into app/views/taglibs/application are > autoloaded. That allows you to split big and messy application.dryml files > into more consistent files: a common use is having one file for each model, > and eventually a few other files for general taglibs that you don't want to > keep in application.dryml.
I'm curious - how does this interact with the subsite mechanism? For instance, I've got a site that has the <page> tag defined differently in admin_site.dryml, jobs_site.dryml and front_site.dryml. Mind you, I could never quite follow how the whole subsite thing worked in the first place (thankfully, it just worked)... --Matt Jones -- 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.
