Design Review on Friday..

[Will Schroeder]

Hi Folks-

GE & Kitware met for an architecture design review on Friday. If you're interested in some of the topics, there are PowerPoint slides in Insight/Documents/DesignReview (you'll want to do a "cvs update -d"). Look for DRApril2000.ppt.

Some of the questions we left the meeting with were:

* For some of you C++ hackers out there, can you tell us if (and how) there is a way to create templated filters that enforce as input an image of a certain dimension? (The itkImage class is currently templated over type and dimension. The filters are templated over input and output (the input & outputs are presumed to be a type of image - but dimension is not enforced.) Can it be done using some trait mechanism?

* Naming conventions: STL and many other packages use a naming convention with lowercase/underscore (get_the_variable). Since we are likely to use STL heavily (and maybe make the itkImage class STL compatible!?) this will result in a mix of naming conventions (Insight currently uses mixed Upper/Lowercase). Questions:
	- do we mix naming conventions? This has the advantage of indicating Insight code versus "external" code. However, if we add STL interface into the Insight classes, then we have the uncomfortable situation of having mixed naming conventions in the same class. (I suppose that we could get around this by introducing specific STL subclasses.)
	- do we adopt STL naming conventions?

Comments / questions / etc. are welcome.

Will