Re[2]: [Templates] Odd....
[prev]
[thread]
[next]
[Date index for 2004/07/02]
DH> sure. If I re-write it (which I will if no one objects), ttree might
DH> just become a wrapper around tsite -p ttree, but the input (options,
DH> etc) and output will stay the same.
My view is that TTree should be a module upon which a ttree script is
written. This way you can utilize a TTree module within other scripts.
I had posted to the TT3 mailing list with this suggestion for several
reasons listed below:
# pre and post process directories and files
# have better control of all TT of options
# manage multiple sites simultaneously using a single script
# using other tools such as html lint
# running queries for semi-static pages
# writing breadcrumbs, site maps, and creating indices for searches
# running template configuration processes such as getting a config
# from a database
Many of these things can be done in other ways but I can envision a
more elegant way using a TTree module.
I've actually written a Template::TTree module early in the year but
ran out of steam when I got buried with other things. It simply
modularizes the ttree script, doesn't handle the command-line, and has
not been fully debugged or documented.
I will clean it up a little over the weekend and submit it to the list
as at least a base to work from.
-Chris
Thursday, July 1, 2004, 2:50:10 PM, you wrote:
DH> On Thu, 1 Jul 2004 09:54:52 -0400, Vivek Khera <khera@xxxxxxx.xxx> wrote:
>>
>>
>> On Jul 1, 2004, at 7:47 AM, Andy Wardley wrote:
>>
>> > It invokes your name and hands you the slaughtered remains of ttree as
>> > a
>> > sacrificial offering. :-)
>> >
>>
>> I certainly hope someone keeps up ttree... One of my OSCON
>> presentations at the end of the month is on using ttree and persistent
>> perl to make websites. :-)
DH> sure. If I re-write it (which I will if no one objects), ttree might
DH> just become a wrapper around tsite -p ttree, but the input (options,
DH> etc)
DH> and output will stay the same.
DH> The only problem with ttree is it has grown too large to easily
DH> maintain or add new features to. a more modular script is needed. :-)
DH> Anyway, I rely on ttree for a number of websites, so it won't change that much.
DH> _______________________________________________
DH> templates mailing list
DH> templates@xxxxxxxxxxxxxxxx.xxx
DH> http://lists.template-toolkit.org/mailman/listinfo/templates
--
Best regards,
Christopher mailto:christopher@xxxxxxx.xxx
_______________________________________________
templates mailing list
templates@xxxxxxxxxxxxxxxx.xxx
http://lists.template-toolkit.org/mailman/listinfo/templates
 |
(message missing)
|