Dave Howorth:
> Umm, why do you need a symlink. Why not just set config->template_root?
> For the factory path; the application's custom path will be somewhere
> else, of course.
You can't set "config->template_root for the factory path". template_root
is not just "for the factory path", but it *is* the application's custom path.
Two situations: In situation one, the user is using the factory templates
and customizing. He has a template root like this:
templates/
some_table/
factory -> symlink
In the second situation, building a real application, we don't even want to
see the factory templates. His template root looks like this:
templates/
some_table/
So we don't have separate template roots for the factory and custom templates,
but if we did, that would be a Bad Thing - it would make it harder than just
a simple "rm" to say that we don't want to use the factory templates.
--
There's no cinnamon and no lemon or orange involved. If there were, it was a
heretic who mixed it up and the mixer should be impaled on a stake and buggered
by the Shrike for two hours, then taken down and forced to rub the wounds with
the mix until death sets in. - Ingvar Mattsson *cares* about cocktails.
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Maypole-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maypole-devel
