[Insight-developers] PathToImageFilter issues

[Miller, James V (GE, Research)]

Zachary, 

I think posting the classes on the Insight Journal would allow a number of people
to evaluate the changes.  Already I would be tempted to rename TracePathOnImageFilter
to TracePathImageFilter.

We are about to lock down the repository (if it wasn't already done last night)
in preparation of the next release.  Your changes may have to wait until the
repository re-opens after the release is tagged.

Jim

-----Original Message-----
From: insight-developers-bounces+millerjv=crd.ge.com at itk.org
[mailto:insight-developers-bounces+millerjv=crd.ge.com at itk.org]On Behalf
Of Zachary Pincus
Sent: Monday, February 13, 2006 11:33 AM
To: insight-developers at itk.org
Cc: Lorensen, William E (GE, Research)
Subject: Re: [Insight-developers] PathToImageFilter issues


Hi folks,

I've re-worked (in what I think is a 100% backward-compatible way)  
the PathToImageFilter class to deal with the issues that I brought up  
last week. Should I go ahead and commit the new class (and a new  
subclass, TracePathOnImageFilter, which has the functionality that  
has been deprecated from PathToImageFilter)?

Perhaps it would be better if I send the classes to someone else for  
review to make sure I haven't broken compatibility, abused ITK  
convention, etc? (To avoid a re-play of the issue of having an  
incorrectly-defined base class in the future.) Any volunteers?

Zach
_______________________________________________
Insight-developers mailing list
Insight-developers at itk.org
http://www.itk.org/mailman/listinfo/insight-developers