That sounds like a plan. Perhaps I should add a paragraph on PySide6 to the latest plugin dev manual and try to also discourage Tk there as well.
Quote:
Originally Posted by DiapDealer
I have no problem with leaving tkinter in the bundles. Doing so on Linux and Windows is not that difficult. But I would like to strongly discourage its use for new plugins.
I never warmed up to tkinter gui programming. In fact, I probably hate it. Getting it to do the things I wanted it to do (in a consistent cross-platform manner) was as painful to me as I imagine self-dentistry would be. I consider it vastly more difficult to work with than PySide/PyQt. But perhaps that's because I understand Qt from the C++ side.
There's no real pressure to make a decision on this, so why don't we let it stew a bit, and upgrade the plugins that are under our control to PySide6? Offer help to those who show an interest in migrating. I figure the more PySide plugin code out there, the more likely it is that plugin devs will use that code for their new plugins.
I know a lot of people used my first tkinter plugins as templates/guidelines. I would have done the same in their shoes. We only had tkinter for while. That's why I bit the bullet and learned a bit about it. But when we started including PyQt, I jumped ship pretty quickly.
|