On Thu, 18 Jan 2007, Bill Moseley wrote:
I currently have most templates (TT) on disk -- and many I'd consider
to be an integral part of the application and are thus under revision
control with the rest of the application.
But, it would make managing the running application a bit easier if
On Sat, Jan 20, 2007 at 02:25:39PM +, Jess Robinson wrote:
I have plans to do that (which went as far as writing
Template::Provider::DBI and including it in my app), but not actually
using yet.
Can you show the Provider code? Or did you just use some of the code
examples posted to the
On a related note...
When templates are on disk there's a nice hierarchy for
grouping templates. Placing the templates in a table (say keyed by
path name) flattens out the templates name space.
It would be nice to preserve the hierarchy in the UI, so I'm wondering
how best to set that up in the
On Sat, 20 Jan 2007, Bill Moseley wrote:
On Sat, Jan 20, 2007 at 02:25:39PM +, Jess Robinson wrote:
I have plans to do that (which went as far as writing
Template::Provider::DBI and including it in my app), but not actually
using yet.
Can you show the Provider code? Or did you just
On Sat, Jan 20, 2007 at 10:13:13PM +, Jess Robinson wrote:
I kept meaning to upload it to CPAN, once TT 2.15 was out.. so now I have
(it should go in the TT repository eventually..) I needed to patch
Template::Provider to make the code somewhat saner, which got into 2.15.
Yes, it does
Bill Moseley wrote:
I currently have most templates (TT) on disk -- and many I'd consider
to be an integral part of the application and are thus under revision
control with the rest of the application.
But, it would make managing the running application a bit easier if
the templates were
On Jan 18, 2007, at 3:22 PM, Bill Moseley wrote:
I do maintain a history of these pages, and I have a crude diff view
using Algorithm::Diff. I have a table that holds the history of the
content and use triggers to write to it on update.
Is this how you are (or would) do this?
I am doing post
