That works for me, but I'm not necessarily thilled at having to specify a template directory everytime a create something new. I was thinking along the lines of "if there's a code_templates directory in your app (same level as webapp directory), use those as overrides."
worse/better? I guess the benefit of your way would be I could have multiple dirs of templates and be able to pick between them on the fly.. but I'm not sure I'd ever utilize that. --Bob On 8/7/05, Mike Vincent <[EMAIL PROTECTED]> wrote: > I've added a ticket for this issue, > http://trac.agavi.org/trac.cgi/ticket/49. I may knock it out here in a > little bit. Basicly just query for the code_template dir to use, > defaulting to the std dir and if you specifiy a custom dir, any > templates in it will take precedence over the std templates. > > > -Mike > _______________________________________________ > agavi-dev mailing list > [email protected] > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
