<div dir="ltr">Hi,<div><br></div><div>An advice would be: </div><div> do not start your project from scratch (except if you intend to use a new (revolutionary) technology). </div><div><br></div><div>
There are many opensource (BSD like ) ITK and VTK based frameworks you can start from. The most popular/advanced allow you to extend them and sometimes to customize and redesign the entire front end GUI while reusing the internals.</div>
<div><br></div><div>Here are some of those ITK/VTK frameworks: 3D Slicer, ParaView, VolView, MITK, GIMIAS, MAF...</div>
<div><br></div><div>Each framework has pros and cons, you probably need to review each of them (and/or contact their mailing lists) to find the one that is closest to you needs. You can also use <a href="http://www.ohloh.net" target="_blank">http://www.ohloh.net</a> to see how advanced, popular and active each project is.</div>
<div><br></div><div>Note also the resourceful webinar: <a href="http://vimeo.com/64823685" target="_blank">Building Qt-enabled VTK applications</a> </div><div><br></div><div>Hth,</div><div>Julien.</div><div>
<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 11, 2013 at 10:55 AM, chasank <span dir="ltr"><<a href="mailto:chasank@gmail.com" target="_blank">chasank@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
This question is a bit abstract (actually completely), so please bear with<br>
us. We have been using VTK/ITK for 3 months. We will begin to implement a<br>
big medical project, and now we are at the design stage (writing use cases,<br>
designing UML diagrams, etc). However, because of lack of experience in<br>
VTK/ITK project, we cannot foresee what classes we will need to use in our<br>
project. Which precautions do we need to take so that we will not have to<br>
change initial design dramatically?<br>
<br>
For example, in one of our former projects we coded a small medical<br>
application which allows users to display dicom/nifti image data for<br>
3-planes (sagittal, coronal, axial) and to select a dynamic roi with seed<br>
region grow filter. But after that, we needed to add oblique slicing feature<br>
to this project and we had to code from scratch. We do not want to have this<br>
struggle in the future again. Do you have any advice for us based on your<br>
precious experiences?<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://vtk.1045678.n5.nabble.com/A-general-advice-for-design-stage-of-a-new-project-tp5721320.html" target="_blank">http://vtk.1045678.n5.nabble.com/A-general-advice-for-design-stage-of-a-new-project-tp5721320.html</a><br>
Sent from the VTK - Users mailing list archive at Nabble.com.<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the VTK FAQ at: <a href="http://www.vtk.org/Wiki/VTK_FAQ" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtkusers" target="_blank">http://www.vtk.org/mailman/listinfo/vtkusers</a><br>
</blockquote></div><br></div></div>