I've been looking at C4/Letters.pm as the templating fails to generate useful output for claimissues. I can certainly get it to work with some code changes but I started wondering if a better use of long term effort might be to replace the home grown templating with a tried and tested perl module. It could use Template Toolkit for instance without changing the user interface, but resulting in more maintainable code. Thought I'd float that suggestion for comments. Cheers Colin -- Colin Campbell Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 208 366 1295 (phone) +44 (0) 7759 633626 (mobile) colin.campbell@ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com
Hi Colin, On Mon, Jul 27, 2009 at 10:14 AM, Colin Campbell<colin.campbell@ptfs-europe.com> wrote:
I've been looking at C4/Letters.pm as the templating fails to generate useful output for claimissues. I can certainly get it to work with some code changes but I started wondering if a better use of long term effort might be to replace the home grown templating with a tried and tested perl module. It could use Template Toolkit for instance without changing the user interface, but resulting in more maintainable code. Thought I'd float that suggestion for comments.
I think switching Template Toolkit would be an excellent choice for the messaging system - the template syntax is simple and clean, and (rather importantly) I can envision writing an upgrade path for the current templates to TT versions of them. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt
2009/7/28 Galen Charlton <galen.charlton@liblime.com>:
Hi Colin,
On Mon, Jul 27, 2009 at 10:14 AM, Colin Campbell<colin.campbell@ptfs-europe.com> wrote:
I've been looking at C4/Letters.pm as the templating fails to generate useful output for claimissues. I can certainly get it to work with some code changes but I started wondering if a better use of long term effort might be to replace the home grown templating with a tried and tested perl module. It could use Template Toolkit for instance without changing the user interface, but resulting in more maintainable code. Thought I'd float that suggestion for comments.
I think switching Template Toolkit would be an excellent choice for the messaging system - the template syntax is simple and clean, and (rather importantly) I can envision writing an upgrade path for the current templates to TT versions of them.
I agree, I think that we may end switching all our templates to TT eventually, starting with the ones that are homegrown seems the perfect place. I did start on converting one template to use TT and started a module that may be some use http://git.workbuffer.org/cgi-bin/gitweb.cgi?p=koha.git;a=tree;f=lib/Koha;hb... Feel free to use anything from there that is useful Chris
participants (3)
-
Chris Cormack -
Colin Campbell -
Galen Charlton