<div dir="ltr"><div>+1 for Matt's proposal.<br><br></div>JON HAITZ<br><br><div><div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><table style="color:rgb(0,0,0);font-family:'Times New Roman';font-size:medium" cellspacing="0" cellpadding="0" border="0" align="center"><tbody><tr><td></td></tr></tbody></table><pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">--<br><br></pre><div><div dir="ltr"></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On 20 September 2017 at 15:16, Matt McCormick <span dir="ltr"><<a href="mailto:matt.mccormick@kitware.com" target="_blank">matt.mccormick@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Toby,<br>
<br>
Thanks again for the contribution.<br>
<br>
Yes, a small follow-up patch in UseITK.cmake will do the trick. For a<br>
large addition like this, some follow-up effort is expected.<br>
<br>
In my opinion, "2dseq" is obscure enough that the addition of "Bruker"<br>
helps identify the class.<br>
<br>
Thanks,<br>
Matt<br>
<div class="HOEnZb"><div class="h5"><br>
On Wed, Sep 20, 2017 at 8:43 AM, Wood, Tobias <<a href="mailto:tobias.wood@kcl.ac.uk">tobias.wood@kcl.ac.uk</a>> wrote:<br>
> Hello,<br>
><br>
> I updated my local copy of ITK to master to test my Bruker patch that was merged a couple of weeks ago. Unfortunately my patch did not change the UseITK.cmake to follow the new name of the module (it was suggested to me that the module name be shortened in case of anymore Bruker formats), so the Bruker reader is not correctly registered.<br>
><br>
> I think I have worked out the required changes to UseITK.cmake, so can submit a patch. However, this raises the question of whether the naming scheme could be rationalized further. Before, both module and class were called “Bruker2DSEQ”. The module is now “Bruker”, and the class is “Bruker2dseq”, which is the correct capitalisation for the format. Should the class/format be shortened to just “2dseq”?<br>
><br>
> I’m sorry not to catch this before my original patch was merged. Changing the name was one of the last things I did, and because the tests explicitly register the ImageIOFactory, they would not pick this up.<br>
><br>
> Best wishes,<br>
> Toby<br>
><br>
> ______________________________<wbr>_________________<br>
> Community mailing list<br>
> <a href="mailto:Community@itk.org">Community@itk.org</a><br>
> <a href="http://public.kitware.com/mailman/listinfo/community" rel="noreferrer" target="_blank">http://public.kitware.com/<wbr>mailman/listinfo/community</a><br>
______________________________<wbr>_________________<br>
Community mailing list<br>
<a href="mailto:Community@itk.org">Community@itk.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/community" rel="noreferrer" target="_blank">http://public.kitware.com/<wbr>mailman/listinfo/community</a><br>
</div></div></blockquote></div><br></div></div></div></div>