Repository navigation
giving WPPM a non-Qt gui option #834
Description
It's time to explore a non-Qt gui option for wppm, that must be small enough to fit in the ".dot"
version
options:
- tkinter,
- flask, (learning the rest ropes, yet to get it work, you need to add a lot of small packages)
- PySimpleGUI
- remi
- ... ?
functionnalities of wppm gui:
- show list of packages and names of a given winpython directory (or let simply to current)
- allow to select a wheel to install. (drag & drop)
- allow to remove a wheel from install (checkmark)
- standalone (no internet required)
- small would be a bonus (so can feed into a dot version)
- is a move forward rather than a tkinter development
contributors ideas are welcomed.
Activity
stonebig commentedon Apr 10, 2020
in the process of looking at it:
stonebig commentedon Apr 17, 2020
thinking to use sqlite with json1 extension, now available in Python-3.9
hiccup7 commentedon Jul 3, 2020
Another reason for non-Qt gui option is that wppm could then be used to change versions of PyQt or PySide2.
I don't like Remi because it requires compatibility with all web browsers where WinPython may be installed. A very difficult thing. Also, a properly-secured web browser should be isolated from anything that can install software.
Since WinPython is released with alpha and beta versions of Python, it would frustrating to find that a gui package doesn't work with these Python versions. For example, see https://github.com/PySimpleGUI/PySimpleGUI#python-37 It doesn't work with Python 3.7.3 or later.
I propose that wppm use Tkinter, which is included in the standard (built-in) library. If wppm uses any package for the gui, then that package cannot be changed with wppm. Tkinter has the highest probability of working correctly in alpha and beta versions of Python.
Translating the current wppm from Qt to Tkinter may be a good project for a student. Removing the requirement for drag-n-drop may help the project succeed for the first release.
stonebig commentedon Jul 4, 2020
It already works with pyside2.
Tkinter problem is zero appeal/zero future: nobody sane will invest time specifically targeting it.
hiccup7 commentedon Jul 5, 2020
What works for PySide2, which doesn't work for PyQt?
przemororo commentedon Nov 15, 2020
Perhaps option with update package via pip and checking packages updates will be good feature
stonebig commentedon Nov 15, 2020
You can use pip already, the GUI was just a basic layer over pip .
I'm not so sure the current GUI makes much sense nowadays, and with pip new resolver it may even be harmfull.
My hope/push is to make pip json friendly and api friendly, so it can be easily completed with an html front-end by a motivated millennial.
17 remaining items
stonebig commentedon Jul 3, 2022
Yesterday trying to click to de-install, the checkmark was not displayed, so my remark
firai commentedon Jul 3, 2022
Seems to be a bug/incompatibility with Pyside6 6.3.1. The checkboxes don't respond correctly on CPython (at least 3.10) either.
Edit: And the checkboxes seem to work correctly with Pyside6 6.3.0 on PyPy.
stonebig commentedon Jul 3, 2022
Would you mind posting your discovery on gitter of pyside ?
firai commentedon Jul 4, 2022
I think I found a fix for PySide6 6.3 (#1083), but I haven't tested the fix against PyQt5 (or the other variants) yet. Unfortunately, I might not have time to so for several days. If you're able to test the patch against PyQt5, that would be great.
stonebig commentedon Jan 24, 2023
wppm has the basic options, in line command... still a webapi or more refinements shall be interesting over that
stonebig commentedon May 4, 2025
at the moment, still no clear solution of what a "simple" gui shall be, that won't hurt maintainance.
chrisrodrigue commentedon Aug 18, 2025
Here's a simple comparison table of 4 mature GUI libraries that I know about.