# Dynamic GUI Generation for Python Plugins
**URL:** https://discourse.paraview.org/t/dynamic-gui-generation-for-python-plugins/17723
**Category:** Feature Requests
**Tags:** python
**Created:** [September 12, 2026, 3:08pm UTC](https://discourse.paraview.org/t/dynamic-gui-generation-for-python-plugins/17723 "2026-09-12T15:08:14Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Felipe\_Bordeu](https://discourse.paraview.org/u/Felipe_Bordeu)
#### Post date: [September 12, 2026, 3:08pm UTC](https://discourse.paraview.org/t/dynamic-gui-generation-for-python-plugins/17723/1 "2026-09-12T15:08:14Z")
Hi ParaView Community,
I do a lot of prototyping, and one feature I use heavily is Python plugins in ParaView.
They make it possible to turn a prototype into something that instantly looks and feels professional, thanks to ParaView’s existing UI and infrastructure.
One thing I really miss, however, is the ability to dynamically create forms and widgets for Python sources and filters. In some cases, the form that should be presented to the user depends on information coming from a file or a network connection, so the required GUI cannot be fully defined in advance.
The new ONNX filter seems to provide part of a possible solution, as it appears to generate GUI elements from a JSON definition.
How difficult would it be to support a truly dynamic GUI for a Python plugin in ParaView, where properties or widgets could be created or updated at runtime based on external data?
I understand that some C++ development would probably be required to support this.
Would this be feasible within ParaView’s current plugin/property architecture?
Thanks, and Thanks the Kitware team for all the great software.
Felipe
---
### Author:  [@nicolas.vuaille](https://discourse.paraview.org/u/nicolas.vuaille)
#### Post date: [September 14, 2026, 9:31am UTC](https://discourse.paraview.org/t/dynamic-gui-generation-for-python-plugins/17723/2 "2026-09-14T09:31:23Z")
Hi @Felipe_Bordeu ,
This is a question that raises more than once those time! I recently did some internal prototype in this context, I hope this may be usable/shareable at some point. This indeed involves C++ dev.
Using this from pure Python plugin maybe challenging too, but doable.
So, short answer is: not doable today but some works in progress.
Concerning ONNX, please note that it is a specific case: it is actually a single property in which we serialize every parameters. The dynamic part is the number of elements for this property. Then we wrote a dedicated C++ code to handle the widgets generation and link them to the single property.