Hi,

we also really appreciate the TT option to have in notices. We tried it and faced a problem especially with those digest letters. If you use digests only, most of the letter is prepared for the first round and then its updated with iterated data items as they come. This means that placeholders like <<count>> are not updated anymore so we can see letters saying eg. "you returned 3 items", but in the fact there is much more of them listed in:
----
<<biblio.title>>
----
Maybe it's a bug and not a TT issue...?

Regards
Radek

Dne 04.01.17 v 8:24 Katrin napsal(a):
+1 to what Bob said. I think we need the old syntax to be fully working at least for a longer transition time.

I can see that TT will allow us to have even nicer notices than we have now, so looking forward to having the option.

I think documentation will be really important in order to have libraries use the feature. We have some special constructs with the current syntax now. It would be nice to have mapping on how to achieve the same output or similar with the new TT syntax. I am thinking of things like:

<<date_due|dateonly>>
<<today>>
<item><<items.fine>></item>
<<items.content>>
...

Katrin

On 03.01.2017 12:40, Bob Birchall wrote:
Its good to see the commitment to keeping the existing syntax as an alternative to the new syntax - thank you!. There are a massive number of existing notice templates in Koha libraries and libraries could face a significant cost to switch to the new syntax. So as long as the path involves introducing the new but retaining the old as an alternative, we're in favour.
Thanks for the initiative.
Bob Birchall
Calyx

On 02/01/17 22:01, Jonathan Druart wrote:
Silence will be considered as an agreement.
If you have any questions, please do not hesitate to ask.

Regards,
Jonathan

On Tue, 6 Dec 2016 at 16:03 Kyle Hall <kyle.m.h...@gmail.com> wrote:

Hey All!

As you may know, Koha 16.11 supports the use of Template Toolkit markup in
Koha's slips and notices. This provides huge benefits over our current
bespoke syntax, such as
A) Consistency, we have odd tags like <<itemscontent>>
B) Flow control, for example, we can hide labels for fields that are empty C) Flexible, for example, maybe you want to mask part of a patrons name on
a print slip, with TT it's easy!

Jonathan and I would really like to get moving on making Template Toolkit
the defacto way to deal with slips and notices in Koha. This is not a
trivial undertaking, and we'd like to get it done in time for the 17.05
release.

To do this we will:
A) Port all slips and notices to TT syntax
B) Enable TT syntax in the slips and notices editor
C) Document the new TT syntax of slips and notices

These tasks will be accomplished on bugs 15278, 15277, and 15276
respectively.

I would like to stress that the existing Slips and Notices syntax will
continue to work in 17.05, and you will *not* need to update your existing
templates during the 17.05 upgrade process.

We are looking for community input on this project before we proceed. Let
us know what you think!

Kyle

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )
_______________________________________________
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

_______________________________________________
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

_______________________________________________
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

_______________________________________________
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


_______________________________________________
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Reply via email to