Open FedorSteeman opened 2 years ago
As for some additional considerations:
Kim mentioned PySide as a possible option: https://wiki.qt.io/Qt_for_Python
@jlegind I'd like some proper dropdownlists instead of the current comboboxes. It should not be made possible to write new entries in the field! And also, I would like the contents of the dropdownlist to be key-value tuples, so we don't need to check the db for the primary key.
Intermezzo: If we decide to change GUI framework midstream, then I lean towards Pythonwx. This is partly due to the license which is Library General Public Licence . The major restriction here is that software built with wx must be open source, which I believe we have already committed to. Wx can do list boxes with up/down arrow navigation and Enter/Return submissions. It remains to be investigated how well Wx does layout.
@jlegind Could you make a tiny test app in wxPython to demonstrate how we can work with its controls, especially list-based ones?
Put on hold depending on outcome of #136 and #95
As we have already done some investigation on this, could we not put the results of that here for future reference @FedorSteeman @jlegind ?
Yes, and Jan mainly did this investigation. However, I also don't want to spend too much time on this right now. If we can get a functional and intuitive pop-up out-of-the-box with the current framework, I still need more reasons for the shift.
We may yet consider this one: https://www.qt.io/qt-for-python
UPDATE: Bhupjit and I have investigated web solutions that will be running locally. The framework FastAPI shows promise and the front end can be HTML and that gives us unprecedented control over the look and feel of the app UI. Advantages:
Disadvantages:
I still firmly believe that the upsides outweigh the downsides.
The new GUI framework must , as a minimum, have the following capabilities: