[Insight-developers] Great examples

[Luis Ibanez]

Hans,

Thanks for pointing out the importance of showing
users how to transition from other programming
paradigms.

We have been immersed in this so long now that we
take for granted a number of practices and intuitions
on how to do things.

The FAQ could be a good place to put such descriptions
but it seems that in practice very few people explore
the FAQ (unfortunately).

I would think in adding a section to the software guide
with a title like "Transition to ITK" or something along
those lines. This section could have something like a
collection of "common mistakes" that people make when
starting with ITK.

Eg.  trying to use the image of filter->GetOutput() without
      having called Update();

or just what Radhika did: disconecting filter
for pluging them farther in the pipeline.

or running CMake in a subdirectory of the source
tree.



We could collect such cases from the users-list archives.

There are a number of topics scheduled to be added to
the SoftwareGuide for a future second edition. That may
still be six months to one year away from now...



   Luis


-------------------------
Hans J. Johnson wrote:
> Luis & Jim,
> 
> The exchange of e-mails between you, and Radhika, does a great job of
> explaining one of the major stumbling blocks in getting new people to
> use ITK.  I've run into this myself in helping others to incorporate a
> small peice of ITK with existing applications, without a complete
> understanding the ITK pipeline.
> 
> In particular, when refactoring legacy code to ITK, it is critical that
> one can use the ITK functionality in a proceedural manner as a stepping
> stone to moving it to a pipeline structure.  I've seen a couple of
> programmers (including myself) spend many days trying to figure out how
> to get one aspect of ITK (i.e. a single filter) to work in old
> procedural code because we made the same mistake that Radhika did.
> 
> Would you please collect these examples and put them into the FAQ?  Even
> better, an example that is included in the pipeline section of the ITK
> software guide would clear up a lot of questions.
> 
> Just my 2 cents, but this is the best explanation that I've seen so
> far.  It could just be that after wrestling with this for so long that
> this example was the one that made it all click.
> 
> Thanks,
> Hans J. Johnson
> 
> 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at itk . org
> http://www . itk . org/mailman/listinfo/insight-developers
>