Developer Announcement - Qt 5.15 available for app developer testing

I have the same views on this as with all the other duplicate stuff (encryption, fingerprints etc) the community has to work for.

It holds the OS back, makes the devs and community unhappy and wastes extremely limited resources.

1 Like

The idea here is to bring the platform forward a little

4 Likes

Maybe the missing protocols could be added using wlroots? Is the compositor actually open source?

I failed to find qt-runner, could you add a link please? Edit: GitHub - rinigus/qt-runner

qt-runner is on chum

4 Likes

So, over the last few days weā€™ve added:

  • qtnetworkauth
  • qtscxml
  • qtgamepad
  • qtdatavis3d
  • qtmultimedia
    When @rinigus has finished his great work on QtWebEngine and QtWebView, we will have all the libs from Qt weā€™re interested in!
5 Likes

Also looks like KDE6 is going to depend on QT6.5 for some recent wayland compositer restart functions recemtly developed.

Ah, so all thatā€™s left is to reverse silica. cool.

1 Like

Could Jolla at one point provide a compiled version of silica on top of this optified Qt version ? As a side by side package to the official system oneā€¦

5 Likes

Potentially ā€¦ a good question for Jolla at a community meeting?

5 Likes

An alternative would be to work on styling Kirigami apps to look like Silica. Or at least similar. That way we can stay with open source components and be compatible with Plasma Mobile

10 Likes

I try to build an app against qt5.15 using latest SFDK and there is something wrong with spec macros and its paths.Using:

%build
%{opt_qmake_qt5}
%make_build

building exits with

+ QTDIR=/opt/qt5
+ /opt/qt5/bin/qmake
Usage: /opt/qt5/bin/qmake [mode] [options] [files]

and Iā€™ve found that it is path issue and when I use

%build
cd ./.sfdk/src
%{opt_qmake_qt5}
%make_build

the app builds in its directory(instead of working) but then fails at %install stage.
What am I missing?

That looks the same as in Add support for out-of-tree mb2 building of the apps Ā· Issue #9 Ā· sailfishos-chum/qt5 Ā· GitHub

No idea what is missing, though

So, I tested running wayland compositor inside qt-runner and ā€¦ it works. Tested using pure QML compositor shown as an example at qtwayland/examples/wayland/pure-qml at 5.15 Ā· qt/qtwayland Ā· GitHub

As a result, it was possible to run apps inside that nested compositor and it allowed to use newer Wayland protocols. The drawback that I saw was a loss of WebGL in QtWebengine, there could be more. But, in principle, as long as compositor is from Qt - Qt is the one supporting the old protocol - it is possible to get newer compositor protocols supported too.

It is even possible to run Silica apps inside that compositor. Just there are some odd aspects, such as transparent background.

2 Likes

I used the new Qt version to make a compositor (really a simple adaptation of the Qt example qwindow-compositor) that creates a new window for each client window (so that apps can open new windows and can open confirmation dialogues when closed).

I also plan to eventually add Xwayland (rootless) integration so we can have X apps as individual windows in Sailfish OS.

https://openrepos.net/content/artur/newcompositor

8 Likes

Havenā€™t yet tested it, but sounds very elegant. For keyboard, I suggest to use the same plugin I am using for qt-runner: GitHub - sailfishos-chum/qt-sfos-maliit-platforminputcontext

But that plugin need DBUS link var that has to be forwarded to the app running in new compositor. It also forward screen orientation to take that into account, probably useful info for the compositor as well.

Alternative would be to use newer Maliit or Qt virt keyboard.

Looking forward to see what comes out of it!

PS: Donā€™t forget to add LICENSE into the repo :slight_smile:

2 Likes

Sounds good only at hearing it. Lined up to see what comes out! :slight_smile:

The Qt packages have been submitted to chum:testing, and are being built for 4.5.0.19. If all goes well, they will go to chum main tomorrow. This is everything except qwebengine, which has some issues to iron out.

6 Likes

Qt packages are now in Chum main, and to help developers more, the sample app has been updated with improvements to install location, how qml files are handled and improvements to the .spec

8 Likes

Kirigami 2 is coming along :slight_smile:

8 Likes

This is not really a request, but it would be nice to be able to make Android and SFOS apps from the same primarily SFOS base.
It would be nice to have a template (examples) for doing this, and building for Android, if one of you were to find it useful to do. (In the first instance QML/JS apps)

Currently the X10iii is not usable where/when I want to use the apps I want to make (due to power drain and GPS), so until (if ever) I have to use the Android.
This makes it pointless to write for SFOS alone since I canā€™t use them