# Workflow that brings together a few modules as tabs in a unifying parent module.

**URL:** <https://discourse.slicer.org/t/workflow-that-brings-together-a-few-modules-as-tabs-in-a-unifying-parent-module/5314>\
**Category:** Development\
**Created:** [January 8, 2019, 8:54pm UTC](https://discourse.slicer.org/t/workflow-that-brings-together-a-few-modules-as-tabs-in-a-unifying-parent-module/5314 "2019-01-08T20:54:48Z")\
**Posts on this page:** 1\
**Showing post:** 14

<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:** [January 10, 2019, 5:37pm UTC](https://discourse.slicer.org/t/workflow-that-brings-together-a-few-modules-as-tabs-in-a-unifying-parent-module/5314/14 "2019-01-10T17:37:59Z")

</div>

I’ve tried to update the current scripted module template to use a .ui file to generate GUI and it worked really well. It reduced and simplified the code a lot.

Reload works nicely: to update the GUI, it is enough to save the .ui file in Qt Designer and click Reload in Slicer.

Widget variables can be automatically exposed as `self.ui.myWidget` (similarly how variables are accessible in C++ by generating a skeleton file).

I’ve submitted a pull request so that you can have a look: [https://github.com/Slicer/Slicer/pull/1072/files#diff-c12bcbe4f4bab89847136fc032496bd4R36](https://github.com/Slicer/Slicer/pull/1072/files#diff-c12bcbe4f4bab89847136fc032496bd4R36)

@jcfr It works so nicely that I think it would worth the time adding designer to the package. Could you have a look? If it’s very easy then it might make sense to include it in 4.10.1.

---

_[View the full topic](https://discourse.slicer.org/t/workflow-that-brings-together-a-few-modules-as-tabs-in-a-unifying-parent-module/5314)._