<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Hey all, </div><div><br></div><div>I do some post-processing, I strip the '*' from the extension list, but keep the leading dot, as that's the way we format supported extensions in the read/writer plugins in medInria.<br></div><div>Do you have examples in the wild of CLIs that output XML without the asterisk ? All the ones I have here (niftyreg tools, the CTK test binaries) have asterisks in their extension lists.<br></div><div><br></div><div>Florian<br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>De: </b>"Sascha Zelzer" <s.zelzer@dkfz-heidelberg.de><br><b>À: </b>"Matt Clarkson" <m.clarkson@ucl.ac.uk>, ctk-developers@commontk.org<br><b>Envoyé: </b>Mardi 17 Juin 2014 21:50:31<br><b>Objet: </b>Re: [Ctk-developers] Command Line Modules<br><div><br></div><div class="moz-cite-prefix">Hi,<br> <br> I was curiously waiting for a reply myself. My interpretation of the extensions list for files is the same as Matts, but if people use it differently or just "post-process" the file extensions list to fit their expectations, this would be good to know.<br> <br> Thanks,<br> Sascha<br> <br> On 06/13/2014 10:49 AM, Clarkson, Matt wrote:<br></div><blockquote cite="mid:865FD103-FB81-4C44-91E8-430E6A5C5458@live.ucl.ac.uk">Hi there,<div><br></div><div>please can people clarify something. In the Slicer Execution Model wiki page [1], it says that the list of file extensions should be a comma separated list of extensions, which I read to mean “no asterisks”. So, something like “nii,nii.gz,mha” and NOT “*.nii,*.nii.gz,*.mha”. Also, the CTK XSD file seems to agree with that:</div><div><br></div><div>Can people please reply to me to confirm if they are in agreement/disagreement.</div><div>And even better… please can people test their respective applications, and confirm if this is all working as it should be?</div><div><br></div><div>I think people need to be careful to check both input and output. In many cases, the input side may well be masked by the application. For example, if the application loads an image into memory, and an “input” combo box simply lists the images currently available memory, then you wont be able to check whether a file open dialog box is actually doing as it should be.</div><div><br></div><div>Thanks</div><div><br></div><div>Matt</div><div><br></div><div>[1] <a href="http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation" target="_blank" data-mce-href="http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation">http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation</a><br data-mce-bogus="1"></div><div>[2] <a href="https://github.com/commontk/CTK/blob/master/Libs/CommandLineModules/Core/Resources/ctkCmdLineModule.xsd#L431" target="_blank" data-mce-href="https://github.com/commontk/CTK/blob/master/Libs/CommandLineModules/Core/Resources/ctkCmdLineModule.xsd#L431">https://github.com/commontk/CTK/blob/master/Libs/CommandLineModules/Core/Resources/ctkCmdLineModule.xsd#L431</a><br data-mce-bogus="1"></div><div><br></div></blockquote><br><br>_______________________________________________<br>Ctk-developers mailing list<br>Ctk-developers@public.kitware.com<br>http://public.kitware.com/mailman/listinfo/ctk-developers<br></blockquote><div><br></div></div></body></html>