> > 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. >
The current implementation completely ignores subistes. It's like the taglibs that you drop into the application dir were included at the end of application.dryml, so your subsite overriding works exactly as before. Anyway, your comment makes me think that I could add the same functionality to subsites, so if you would drop any dryml file into e.g. the jobs_site dir, it would be like you included it at the end of jobs_site.dryml, withouth actually adding any include tag. It makes sense and it improves symmetry with the application dir. What do you think? ciao dd -- 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.
