# Creating a module with existing python code

**URL:** <https://discourse.slicer.org/t/creating-a-module-with-existing-python-code/7373>\
**Category:** Support\
**Tags:** extensions-manager\
**Created:** [July 1, 2019, 8:55pm UTC](https://discourse.slicer.org/t/creating-a-module-with-existing-python-code/7373 "2019-07-01T20:55:11Z")\
**Posts on this page:** 1\
**Showing post:** 16

<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:** [July 4, 2019, 7:47pm UTC](https://discourse.slicer.org/t/creating-a-module-with-existing-python-code/7373/16 "2019-07-04T19:47:40Z")

</div>

> [@Jesse](#):
>
> Do you know a good place where I can get familiar with VTK and Qt libraries?

VTK and other medical image computing related libraries: see [this post](https://discourse.slicer.org/t/a-free-biomedical-image-analysis-and-visualization-2-day-course/2584/10).  
Qt: there are many online tutorials and examples.

> [@Jesse](#):
>
> I also looked at the source code of “Fill in between slices” because the concept is quite similar but to my surprice this was only 46 lines long. To me this seems very short.

That’s the point. If you already have a method that computes missing segmentation between segmented slices, then you need to write a few ten lines of code to make it available in Slicer.

---

_[View the full topic](https://discourse.slicer.org/t/creating-a-module-with-existing-python-code/7373)._