Separate GUI and Backend of PySide Widget Program
-
I created a prototype for a program I’m developing using PySide with widgets. I later learned about QML, and from what I understand, one of its main advantages is the inherent separation of the GUI frontend and computation backend.
After experimenting a little with QML, I like it a lot. However, one of the libraries I’m using (PyQtGraph) is a widget-based library, and I have yet to find a QML equivalent. Is there a simple/standard method of separating the frontend and backend of a widget-based program?Any help or guidance is greatly appreciated!
-
I created a prototype for a program I’m developing using PySide with widgets. I later learned about QML, and from what I understand, one of its main advantages is the inherent separation of the GUI frontend and computation backend.
After experimenting a little with QML, I like it a lot. However, one of the libraries I’m using (PyQtGraph) is a widget-based library, and I have yet to find a QML equivalent. Is there a simple/standard method of separating the frontend and backend of a widget-based program?Any help or guidance is greatly appreciated!
@JKC23 said in Separate GUI and Backend of PySide Widget Program:
Is there a simple/standard method of separating the frontend and backend of a widget-based program?
Well, the standard method is to devide your application in layers. The UI would be one layer which communicates with other layers like business logic layer.
Also, take a look at https://doc.qt.io/qt-5/model-view-programming.html
