-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop support for Stretch and Buster #70
Comments
I absolutely agree, thanks. |
Qt5 has a completely different way of dealing with virtual keyboards which I never fully understood. In theory we could probably ignore that altogether if we make sure that text input is always done via some custom widget. The only downside would IMHO be that existing app that use the original input widgets like qlineedit would not have touch support and would have to be slightly modified. |
Here's the part in question: This needs to get replaced somehow. |
I'll see if you can still get Qt4 somewhere. It might have to be compiled during installation, e.g. from here https://download.qt.io/archive/qt/4.8/4.8.7/qt-everywhere-opensource-src-4.8.7.tar.gz I have to see what's less work. ;) First of all, I'm interested in maintaining the status quo. |
It might also be possible to use the Trinity project: https://wiki.trinitydesktop.org/Preliminary_Stable_Builds The project still releases Qt4 for current Debian versions. But I don't know if it still runs under the Qt4 namespace or a fork of Qt4 under a different name. The packages have an additional "t" in the name, so it could be that the namespace is different: https://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb/pool/main-r14/p/pytqt/ But this could easily be fixed. |
Looking ahead, it would probably make more sense to adapt TouchUI. Qt5 reaches EOL in May (https://www.qt.io/blog/qt-5.15-extended-support-for-subscription-license-holders), and the upcoming version of Debian will likely be the last with rudimentary support for Qt5 (https://wiki.debian.org/PkgQtKde/TrixieReleasePlans). |
Trixie is just around the corner, there is no point in continuing to support such old distributions.
I will make a hard cut in the develop branch.
Until the develop branch has stabilized, the setup from the master branch can still be used, if it still works.
The text was updated successfully, but these errors were encountered: