<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Hi all,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I propose that new Koha Plugin Hooks start with a prefix of “hook_”. If you look at <a href="https://wiki.koha-community.org/wiki/Koha_Plugin_Hooks">https://wiki.koha-community.org/wiki/Koha_Plugin_Hooks</a> or the Kitchen Sink plugin, it’s impossible to tell what methods are “hooks” and what are part of the basic plugin core API. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Also, if a hook is going to modify a template directly (<a href="https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27114">https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27114</a> and <a href="https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27120">https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27120</a>), I think we should probably come up with some agreements on how that’s best to work, so we don’t end up with N different approaches for the same intention. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think that <a href="https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26890">https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26890</a> raises some interesting issues about how it’s not easy to modify Koha’s HTML output using plugins. Perhaps we should have a little analysis of some key pages and identify hooks, or do something a bit more complex/comprehensive. (Of course, I already have too many other things I’m working on do a POC for this right now…)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>David Cook<o:p></o:p></p><p class=MsoNormal>Software Engineer<o:p></o:p></p><p class=MsoNormal>Prosentient Systems<o:p></o:p></p><p class=MsoNormal>72/330 Wattle St<o:p></o:p></p><p class=MsoNormal>Ultimo, NSW 2007<o:p></o:p></p><p class=MsoNormal>Australia<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Office: 02 9212 0899<o:p></o:p></p><p class=MsoNormal>Online: 02 8005 0595<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>