Harald Joerg wrote:
> I could submit a patch which

You could, but I think the time has come for ttree to be slaughtered 
like the rabid fox that it has become.  It has been foaming at the 
mouth for some time and we should now do the humane thing.

Kill it!  Kill it!  Kill it!

Oops, sorry, I got carried away.  But don't worry, it's only a bit 
of software - it doesn't have feelings (I hope :-)

Seriously though, the plan for post-TT3 ttree has been to re-architect
it and move it into the Template::Tool::TTree module(s) or something
similar.  I think we should start planning that migration now.

Your welcome to submit a patch in the mean time, but I think the long
term solution is a more robust implementation of ttree.

Dylan Hardison has made motions towards this, although I forget where
we left it last time we talked on the matter.  Dylan, you got any plans
brewing?

The only thoughts that I've thought on this matter are these:

  * The code for reading and writing TT configuration options should 
    be generalised into a Template::Profile module which all the tools
    can use.  Thus tpage will be able to set all the TT options that 
    tree can, for example.  Ttree need only worry about ttree options 
    (like directories, permissions, dependencies, copy rules, etc.), and 
    can have a -p profile, or --profile=profile option (or something 
    similar) which tells ttree which TT configuration profile you to 
    use to set all the TT options (include_path, chomp flags, etc., etc).

  * The traversal code for locating templates should be separate from 
    the ttree processing and output code.  Ideally, we could use the
    provider(s) defined by the current profile to tell us what templates
    are available (e.g. $provider->index()), but that relies on the
    TT3 provider API which isn't quite definitive yet, and doesn't yet
    support anything like this.  Still, it's worth bearing in mind for

Apart from that, I'm open to suggestions.

A


_______________________________________________
templates mailing list
[EMAIL PROTECTED]
http://lists.template-toolkit.org/mailman/listinfo/templates

Reply via email to