<div dir="ltr">I think we have a conflict here of<div><br></div><div>a) Make TT in notices work with the current syntax ( just by replacing << >> with [% %]</div><div><br></div><div>and</div><div><br></div><div>b) Use a flag to decide if it is processed by TT or by the old way of doing things</div><div><br></div><div>I think if we are going to go with b, we should have the freedom to not be beholden to all the oddities and cruft of the current syntax. For this reason I am a fan of b.</div><div><br></div><div>Is anyone opposed to this idea?</div><div><br></div><div>This would give us plenty of time ( all the time we want really ) in which to tweak and perfect the TT based parser before deprecating the current parser.</div><div><br></div><div>If anyone has an issue with this path, please speak now!</div><div><br></div><div>Kyle</div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><a href="http://www.kylehall.info" target="_blank">http://www.kylehall.info</a><br>ByWater Solutions ( <a href="http://bywatersolutions.com" target="_blank">http://bywatersolutions.com</a> )<br>Meadville Public Library ( <a href="http://www.meadvillelibrary.org" target="_blank">http://www.meadvillelibrary.org</a> )<br>Crawford County Federated Library System ( <a href="http://www.ccfls.org" target="_blank">http://www.ccfls.org</a> )<br>Mill Run Technology Solutions ( <a href="http://millruntech.com" target="_blank">http://millruntech.com</a> )<br></div></div>
<br><div class="gmail_quote">On Wed, Feb 3, 2016 at 3:16 PM, Katrin Fischer <span dir="ltr"><<a href="mailto:Katrin.Fischer.83@web.de" target="_blank">Katrin.Fischer.83@web.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I like the idea of the flag as it would allow to keep the code separate<br>
from the current notices code and to have a clean start, while we can be<br>
pretty sure that the old code still remains working as before.<br>
<br>
The current syntax is not very consistent across the different notices -<br>
<<items.content>>, ----, <item></item>... or in which tables/columns can<br>
be included. It would be nice to gain some consistency with this<br>
development :)<br>
<br>
Katrin<br>
<span class=""><br>
Am 03.02.2016 um 20:04 schrieb Barton Chittenden:<br>
> I think that a flag may not even be necessary -- the TT syntax won't<br>
> conflict with the current letter formats, and is unlikely to be entered<br>
> accidentally. I think that we could simply silently start to support TT,<br>
> and no one would be the wiser, except for those who want to use it.<br>
><br>
> This also addresses Heather's concern -- the initial transition would be<br>
> essentially un-noticable.<br>
><br>
> On Wed, Feb 3, 2016 at 10:22 AM, Galen Charlton <<a href="mailto:gmc@esilibrary.com">gmc@esilibrary.com</a><br>
</span><span class="">> <mailto:<a href="mailto:gmc@esilibrary.com">gmc@esilibrary.com</a>>> wrote:<br>
><br>
> Hi,<br>
><br>
> On Wed, Feb 3, 2016 at 8:56 AM, Kyle Hall <<a href="mailto:kyle.m.hall@gmail.com">kyle.m.hall@gmail.com</a><br>
</span><span class="">> <mailto:<a href="mailto:kyle.m.hall@gmail.com">kyle.m.hall@gmail.com</a>>> wrote:<br>
> > I think Jonathan has an excellent plan of attack, but it does require a<br>
> > complete switchover all at once.<br>
><br>
> Rather than forcing a complete switchover right off the bat, I suggest<br>
> adding a flag that specifies whether old-style or TT templates are in<br>
> effect for a given notice. That way, we'll have much more flexibility<br>
> to design the new templating mechanism to take full advantage of<br>
> Template Toolkit, and folks will have the ability to migrate their<br>
> notices definitions on their own schedule.<br>
><br>
> Regards,<br>
><br>
> Galen<br>
> --<br>
> Galen Charlton<br>
> Infrastructure and Added Services Manager<br>
> Equinox Software, Inc. / The Open Source Experts<br>
</span>> email: <a href="mailto:gmc@esilibrary.com">gmc@esilibrary.com</a> <mailto:<a href="mailto:gmc@esilibrary.com">gmc@esilibrary.com</a>><br>
> direct: <a href="tel:%2B1%20770-709-5581" value="+17707095581">+1 770-709-5581</a> <tel:%2B1%20770-709-5581><br>
> cell: <a href="tel:%2B1%20404-984-4366" value="+14049844366">+1 404-984-4366</a> <tel:%2B1%20404-984-4366><br>
<span class="">> skype: gmcharlt<br>
> web: <a href="http://www.esilibrary.com/" rel="noreferrer" target="_blank">http://www.esilibrary.com/</a><br>
> Supporting Koha and Evergreen: <a href="http://koha-community.org" rel="noreferrer" target="_blank">http://koha-community.org</a> &<br>
> <a href="http://evergreen-ils.org" rel="noreferrer" target="_blank">http://evergreen-ils.org</a><br>
> _______________________________________________<br>
> Koha-devel mailing list<br>
> <a href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a><br>
</span>> <mailto:<a href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a>><br>
<div class="HOEnZb"><div class="h5">> <a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
> website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
> git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
> bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Koha-devel mailing list<br>
> <a href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a><br>
> <a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
> website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
> git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
> bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br>
><br>
<br>
_______________________________________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a><br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br>
</div></div></blockquote></div><br></div>