# SlicerQR Development

**URL:** <https://discourse.slicer.org/t/slicerqr-development/15954>\
**Category:** Development\
**Tags:** registration, build, segmentation, dicom, python\
**Created:** [February 11, 2021, 3:59pm UTC](https://discourse.slicer.org/t/slicerqr-development/15954 "2021-02-11T15:59:22Z")\
**Posts on this page:** 1\
**Showing post:** 42

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [February 25, 2021, 6:28am UTC](https://discourse.slicer.org/t/slicerqr-development/15954/42 "2021-02-25T06:28:49Z")

</div>

> [@Slicer custom application deployment to many computers](https://discourse.slicer.org/t/slicer-custom-application-deployment-to-many-computers/18019/38):
>
> might I be able to get the size down significantly smaller than 300MB? Sankhesh’s 2018 FourPanesViewer app was has a total size of 60MB and had similar functionality.

The FourPanesViewer is pure VTK. It has no GUI widgets, no proper DICOM parser, no proper widgets, etc. The Slicer core will not be significantly smaller than 300MB just by removing DLLs, but you would need to reengineer the application. Since 300MB is smaller than a typical image that the user downloads by the dozens and you don’t actually need to deploy the 300MB Slicer, only a 10MB launcher, the effort for reengineering (and maintain the ultra-lean Slicer core) is very hard to justify.

> [@spycolyf](#):
>
> Question: Do you all do anything with A.I. in imaging?

Yes, AI is a very trendy topic, so there is lots of activity around it in the Slicer community, too. This is a good example of why creating an ultra-lean Slicer core would not worth the effort: users would keep asking for enabling features and we would end up using the full Slicer core quite quickly.

---

_[View the full topic](https://discourse.slicer.org/t/slicerqr-development/15954)._