I’m working on a project that needs lots of toolbars on screen at once, even though not all of them will be used at the same time. So, I’m modelling this ‘foldable’ dock widget after what I remember Photoshop panels used to be like.
It’s a work in progress, but would like to hear constructive suggestions.
https://blocks.programming.dev/0101100101/42c5d67f86c049baa3500aa38e439f8a
Think the quote is
premature optimization is the root of all evil. Don’t know who came up with that famous expression.In the case of the code in the process guard, perhaps you are right.
In the case of embedding a class within FoldableDockWidget, it’s simply a case of don’t do that, not optimization.
qasync
Python library for using asyncio in Qt-based applications
^^ is the package to support them all.
This comes directly from an app i wrote,
from qasync import (asyncSlot, QtWidgets, QtGui, QtCore, _make_signaller)Here is some code which deals with differences between implementations
from qasync import (QtWidgets, QtCore, QtGui, QtModuleName) __all__ = ["QtportQAction", "QtportQScreen", "QtportQScreenImplementation"] try: QtportQAction = QtWidgets.QAction except AttributeError as e: #"PySide6", "PyQt6" QtportQAction = QtGui.QAction try: QtportQScreen = QtWidgets.QDesktopWidget QtportQScreenImplementation = "QDesktopWidget" except AttributeError as e: QtportQScreen = QtGui.QScreen QtportQScreenImplementation = "QScreen"So it can be done!
In the case of this gist, it’s premature optimization. Generally it’s necessary cuz new implementations come along often.
That sounds terribly inexperienced. That’s exactly what updates to code are for. You cannot manage all kind of, sort of similar but different libraries with one code base. It would be horrific to even consider it.
The same argument can be made for supporting Windows and MacOS. Don’t have these dev environments. But somehow found a way to support these platforms.
If you look into it, pyQt[x] and pySide[x] aren’t all that different. The intent of PySide is to keep them for the most part compatible.
Don’t have to manage everything, just what is being used.
Doing the wrong thing explains most my packages:
wreck – dependency management
drain-swamp with drain-swamp-action – build backend with build plugins
logging-strict – strictly validated logging configuration
pytest-logging-strict – the same thing except a pytest plugin
What else am i not supposed to do?