[Insight-developers] Design issues regarding I/O

[Bill Hoffman]

I am not sure it does make sense to have the input and output be exactly the
same.   For the input, you need to create a reader based on the type of file
you are trying to read.   For output, you have to specify what type of
output you want in some way as no file exists.  I don't think it is a good
idea to try to pass that information via the output file name.  It will
be safer (no mistakes) and cleaner code to explicitly specify the object
that is going to do the output.   


-Bill


At 10:11 AM 8/16/2002 -0400, Mark Foskey wrote:
>Luis said a while back that getting the object factory working for image
>output "should be on WA5".  Is it?  I think it's important because
>anyone who wants to do output as well as input will want to use the same
>idiom for both.
>
>Also, why does calling Update() on an output object not actually perform
>the write?  This seems inconsistent with the overall design of the
>system.  As it is, Write() calls Update() and then writes the output,
>and Update() just tells the input to update itself.  It would seem more
>consistent if Write() wrote the current contents of the buffer *without*
>updating the input, and Update() updated the pipeline and then called
>Write().  But perhaps I misunderstand the overall design.
>
>-- 
>Mark Foskey    (919) 843-5436   Computer-Aided Diagnosos and Display Lab
>foskey@cs.unc.edu               Department of Radiology, CB 7515, UNC
>http://www.cs.unc.edu/~foskey   Chapel Hill, NC  27599-7515
>
>
>_______________________________________________
>Insight-developers mailing list
>Insight-developers@public.kitware.com
>http://public.kitware.com/mailman/listinfo/insight-developers