lets talk about pyqt6 in the lomri toolkit

developerbayman

as the title says i need some feedback about updating the toolkit ....i have a copy i updated it and i need to to do some things and get some verification on some things .....like i could take this code base and run any direction with it ....but that is not good for the many ....so lets talk about it

gpatel-fr

@developerbayman

shipping QT6 with a click will be blocked by the store at the moment, it needs explicit authorization.

developerbayman

@gpatel-fr how come?

developerbayman

@gpatel-fr ok so i had to think about it for a minute ... ..you mean it will be rejected because it currently does not build against the lomri toolkit so it is technically not supported? ...what i mean is updating the lomri toolkit in UT to make it compatible ........im kinda in the middle of doing this actually but i need to know what people think about it because if i take the code and just do any ol thing it wont be ubuntu touch anymore ......my thought process is im going to bring ubuntu touch up to par with all modern libraries for absolutely everything ....a ultra cutting edge UT build ...im working on two ports right now one for x86_64 and one for the orange pi 5 rk3888s ~when i can ...also ALOT of my software im about to port to ubuntu touch is already pyqt6

gpatel-fr

@developerbayman

what I gathered from the UT Q&A is that there is no fundamental issue with QT6 for Lomiri, it's only that for compatibility reasons it's necessary to support both QT5 and 6 for tuture versions and it's not possible without extending the rootfs for many phones and it's not easy to manage.

For now QT6 is only used with the UT browser morph and it's done by shipping the QT6 libraries via the store, outside of the rootfs. However it is currently not supported without specific authorization from the store.

pparent

@gpatel-fr said:

@developerbayman

shipping QT6 with a click will be blocked by the store at the moment, it needs explicit authorization.

Not sure about that I thought @bhdouglass removed this obligation. At least I've been able to publish my Qt6/QML6 based Touch piano app!

developerbayman

@pparent this is good to know basically 99% of all my stuff is on qt6 i would hate to have to refactor back to qt5

gpatel-fr

@pparent

or your app was added to a white list. Such a thing exists for sure since Morph QT6 was accepted and your app was rejected at first.

pparent

@developerbayman said:

@pparent this is good to know basically 99% of all my stuff is on qt6 i would hate to have to refactor back to qt5

Anyway this is only a question of time before Qt6 gets integrated in the system and become the standard for app development. Now to publish a Qt6 app to the openstore you have to bundle the whole Qt6 library with you're app which might be a bit heavy, be soon this should not be a problem anymore.

developerbayman

lomri toolkit pyqt6 update:

https://drive.google.com/file/d/1VVt93fPzGoiQoIUI-_R2q2qvuehyhZs3/view?usp=sharing

What I changed:

repaired all four Qt 6 *Config.cmake.in files so find_dependency() uses valid CMake syntax
fixed the wrong targets include in LomiriMetrics-Qt6Config.cmake.in
fixed LomiriSystemInfoQt6 to LomiriSystemInfo-Qt6
added the missing Core5Compat dependency in the toolkit package config
fixed the project version drift so the build uses PROJECT_VERSION instead of hard-coding 1.0.0
made private Qt module discovery unconditional in top-level CMake
added 1.3 compatibility aliases to the Qt 6 qmldir files for Lomiri.Components, ListItems, Pickers, and Popups
updated the examples to the canonical Qt 6 2.0 imports
rewrote export_qml_dir.sh and push_to_phone.sh around Qt 6 paths instead of the old Qt 5 layout
improved the PyQt6 runner so it can discover more realistic build/staging layouts
replaced the outdated Qt5/qmake README guidance with Qt6/CMake guidance

idk i used AI to verify the syntax and check all the api calls so it wouldnt break ....lets play around and see what happens

developerbayman

actually this is been a few months coming