<br>Darren,<br><br>This is a very good point.<br><br>Yes, we should encourage contributors to the Insight Journal,<br>to include, not only tests for their classes, but also examples<br>on how to use them. These examples could be integrated in<br>
the Software Guide.<br><br>Examples, tend to be a lot simpler, and are populated with<br>comments that provide practical advice on the use of the classes.<br><br>Your point is well taken: It is important to make sure that <br>
source code that is recommended to the community,<br>is source code that gets compiled and run everyday<br><br><br> Luis<br><br><br>-------------------------------------------------------------------------------<br>
<div class="gmail_quote">On Wed, Jul 1, 2009 at 2:31 AM, Darren Weber <span dir="ltr"><<a href="mailto:darren.weber.lists@gmail.com">darren.weber.lists@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>It seems that a lot of the software guide is coded in the examples, using comments in the example .cxx src. Perhaps contributors for new classes can develop simple examples with similar comments for inclusion in a regular build for the software guide, to provide some degree of updating for the guide. It's fairly simple latex text in the comments. I know most everyone has learned M$ Word these days, but I would imagine latex is still prevalent among the math and comp-sci community. The advantage to this is that the examples can be compiled and distributed with the src code, while the wiki is not.<br>
<br>Take care,<br><font color="#888888">Darren</font><div><div></div><div class="h5"><br><br><br><br><div class="gmail_quote">On Tue, Jun 30, 2009 at 10:04 PM, asamwm <span dir="ltr"><<a href="mailto:asamwm@gmail.com" target="_blank">asamwm@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Luis,<br>since this is all in the spirit of open source community,<br>part of whose growth is credited to people from the <br>community, why not create agree on an architecture<br>for community-based documentation where everyone<br>
who participates in developing/evaluating/using a filter<br>can contribute to the wiki. The journal is a stepping<br>stone but the more detailed, elaborated documentation<br>would be the wiki.<br>There would be fixed sections such as:<br>
general purpose (what problem it attacks, image examples)<br>advantages / why this one ,<br>known disadvantages (why not),<br>how it works (optimization),<br>same category as in (list of other filters)<br>see also (broader area)<br>
code snippets<br>pitfalls<br><br><br>I know one concern is to be careful not to misinform,<br>but this is the beauty of open source. The community<br>will correct falsehoods with time. Besides, this does<br>not need to replace the itksoftwareguide since<br>
that one is specific to the basics.<br><br>Just my 2c.<br>I do not know how everyone feels about this.<br>Please share.<br>Regards.<div><div></div><div><br><br><div class="gmail_quote">On Tue, Jun 30, 2009 at 3:06 PM, Luis Ibanez <span dir="ltr"><<a href="mailto:luis.ibanez@kitware.com" target="_blank">luis.ibanez@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Hi Oliver,<br>
<br>
<br>
<br>
1) Yes, the ITK Software Guide is overdue for an update.<br>
<br>
<br>
2) You can see a manifesto of new filters on the Wiki<br>
page of every release.<br>
<br>
For example:<br>
<br>
<a href="http://www.itk.org/Wiki/ITK_Release_3.14" target="_blank">http://www.itk.org/Wiki/ITK_Release_3.14</a><br>
<a href="http://www.itk.org/Wiki/ITK_Release_3.12" target="_blank">http://www.itk.org/Wiki/ITK_Release_3.12</a><br>
<a href="http://www.itk.org/Wiki/ITK_Release_3.10" target="_blank">http://www.itk.org/Wiki/ITK_Release_3.10</a><br>
....<br>
<br>
<br>
3) Yes, the ITK Software Guide will be updated,<br>
probably in the next year or two.<br>
<br>
<br>
4) Since 2006, All new classes in ITK must have been<br>
described in Insight Journal papers.<br>
<br>
If you need information about a New class,<br>
there must be a paper in the Insight Journal<br>
describing this class.<br>
<br>
<br>
For example, the Chan and Vese level set filters<br>
are described in<br>
<br>
<a href="http://www.midasjournal.org/browse/publication/322" target="_blank">http://www.midasjournal.org/browse/publication/322</a><br>
<br>
<br>
<br>
<br>
Regards,<br>
<br>
<br>
Luis<br>
<br>
<br>
----------------<br>
Oliver Gloger wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello together,<br>
<br>
Is it true that the SoftwareGuide did not change since 2005? On the other hand I can see from the mailing-list that there exist new filters now (i.e. itkScalarChanAndVeseSparseLevelSetImageFilter or other filters, which are not mentioned in the ITKSoftwareGuide). Will the ITKSoftwareGuide be updated? Where can I be informed about how to use new adjoined classes and filters in the ITK?<br>
<br>
best regards <br>
Oliver!<br>
<br>
<br>
<br>
</blockquote>
_____________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at<br>
<a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ITK FAQ at: <a href="http://www.itk.org/Wiki/ITK_FAQ" target="_blank">http://www.itk.org/Wiki/ITK_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.itk.org/mailman/listinfo/insight-users" target="_blank">http://www.itk.org/mailman/listinfo/insight-users</a><br>
</blockquote></div><br>
</div></div><br>_____________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at<br>
<a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ITK FAQ at: <a href="http://www.itk.org/Wiki/ITK_FAQ" target="_blank">http://www.itk.org/Wiki/ITK_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.itk.org/mailman/listinfo/insight-users" target="_blank">http://www.itk.org/mailman/listinfo/insight-users</a><br>
<br></blockquote></div><br>
</div></div><br>_____________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at<br>
<a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ITK FAQ at: <a href="http://www.itk.org/Wiki/ITK_FAQ" target="_blank">http://www.itk.org/Wiki/ITK_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.itk.org/mailman/listinfo/insight-users" target="_blank">http://www.itk.org/mailman/listinfo/insight-users</a><br>
<br></blockquote></div><br>