Improve ITK module type handling

[GoogleCodeExporter]

Currently, most ITK modules default to 3-D float.  This is often wasteful.

Think up a new scheme whereby a module developer can easily:
1. instantiate a default pipeline type
2. re-instantiate if the incoming input is different from the default (and
re-apply the module config)

Output type should be as similar as possible to the input type, unless
that's not logical for the given filter (e.g. the watershed needs to
generate longs on the output)

Original issue reported on code.google.com by cpbotha on 14 Sep 2008 at 8:24

[GoogleCodeExporter]

Original comment by cpbotha on 4 Dec 2008 at 1:04

• Added labels: Milestone-Release8.12

[GoogleCodeExporter]

Original comment by cpbotha on 23 Dec 2008 at 5:36

• Added labels: Milestone-Release9.1

[GoogleCodeExporter]

I've implemented some of this in the watershed.py module.

Original comment by cpbotha on 27 Jan 2009 at 10:14

[GoogleCodeExporter]

I'm tagging this Release3000 as it entails many low-level changes to the ITK 
modules.

Original comment by cpbotha on 27 Jan 2009 at 10:15

• Added labels: Milestone-Release3000
• Removed labels: Milestone-Release9.1