(changed the subject to reflect the slightly shifted topic of the discussion)
Need for a “lightweight” application is a commonly cited reason for starting development of a medical application from scratch (using just VTK+Qt). However, most of the time this is not a well-founded reason.
For example, if you already use Qt and VTK, adding an open-source application framework (3D Slicer, MITK, etc. – if it is not strictly medical application then there are several others, for example ParaView) increases the total amount of third-party libraries (in term of line of source code) by about 5%. This is very little price to pay for the hundreds of man-years of effort that went into development and testing of these frameworks. When you apply for regulatory approval for commercial applications, 3D Slicer is considered software of unknown pedigree, the same way as VTK, and other libraries that you may use. Overall, you get somewhat increased documentation work, but you can save several years of software development effort.
We find that with 3D Slicer you need to write approximately 0.01%-0.1% of application-specific code for a new medical application – see this illustration: https://1drv.ms/b/s!Arm_AFxB9yqHr_hDpop7_CaxXoO4cA.
I know that it is more fun to just start to develop something from scratch, compared to learning from others; it is also useful for understanding details by getting first-hand experience, etc., but when the end result is important – you want to have an application that clinicians can use, try a new method in the operating room, you want to release a product faster, etc. – then it is hard to justify the duplicated effort.
I know that the VTK list is read by many people – VTK developers, users, application developers. I would be interested in hearing about opinion and experiences of others. Not necessarily in the medical imaging domain: for example ParaView developers may see a similar trend of people developing custom scientific visualization applications from scratch, instead of customizing/extending ParaView.
From: Bill Q [mailto:[hidden email]]
Thanks a ton!
We are building a software that has a very specific purpose, other than the visualization part, everything else is tailored to the demands. To make it lightweight, we have to build a custom software. That's why we have taken the more difficult approach. Otherwise, we would have chosen an open-source solution.
Thanks again for pointing out the solution.
On Sat, Jul 1, 2017 at 8:36 AM, Andras Lasso <[hidden email]> wrote:
Powered by www.kitware.com
Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the VTK FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
Search the list archives at: http://markmail.org/search/?q=vtkusers
Follow this link to subscribe/unsubscribe:
|Free forum by Nabble||Edit this page|