A Qml6 webapp: Touch piano

gpatel-fr

Tested and approved ! well, at least it did not destroy my phone at first launch. Now I only have to remember my piano lessons of oh so long ago (I hated it).

BTW from what you write, it seems that there are no official guidelines for Store inclusion ?

From the information given by another poster, it was my understanding that any confined application could be uploaded without review, yet your application is confined yet was denied entry by the gatekeepers.

Since you are a prolific click provider, I'd say that you could be entitled to use the next Q&A to ask who is responsible for this function and on which criteria ?

Edit: some warning, the application is locking the phone in landscape mode until stopped

pparent

@gpatel-fr

Well at the same time I understand that using a Qt6 bundle for a piano application is bit overkill (as it would be to use an Electron app for that). Because it makes .click packages way heavier, although next versions would be very light as soon as Qt6 can be integrated into the filesystem. I did not plan to publish any other app with a Qt6 bundle, only because I had spent time to play around for this one I figured I would publish it anyway.

Note that the nice thing with QtWebengine6 vs Electron/XWayland, is that the former is hardware accelerated, while the latter won't be until we can switch have electron apps run on Wayland with Mir2.x .

@bhdouglass If you'r passing by, don't hesitate to explain more the uploading rules!

Some warning, the application is locking the phone in landscape mode until stopped

This is not specific to my app, but happens also with other landscape-only apps. If you switch to another app without stopping this one, it will go back in normal (portrait) mode. It's just an option in the .desktop file. For example if you try this chess clock, it should be the same: https://open-store.io/app/chessclock.jonas . It has nothing to do with it being Qt6!

By the way I realize also that some multi-touch gestures has been added to Lomiri, specifically with 4 fingers, and it seems to me that it's going into the way of using properly multi-touch inside the apps. Sometimes an action is triggered, while I don't seem to have done anything obvious for that.

kugiigi

Confined apps should be allowed without manual review. What's the exact error are you getting? Maybe it times out because it's a bit big? Maybe you can request Brian to upload it for you.

As for the muti touch gestures, yes Lomiri has them for 3-finger (tablets) and 4-finger. Unfortunately, there's no way to disable it yet for each app. I have a custom indicator called Immersive mode but I think it only disabled the edge gestures and I don't even know if it still works on Noble

Lomiri Plus does have the same mode and it disables all gestures except the top edge.

pparent

@kugiigi said:

Confined apps should be allowed without manual review. What's the exact error are you getting? Maybe it times out because it's a bit big?

No, it's not a size problem. It says:

The uploaded click did not pass automated review. Please fix the issues and upload again.

    Unsupported `6.8` version of Qt used: lib/aarch64-linux-gnu/qt6/plugins/wayland-shell-integration/libinputpanel-shell.so

bhdouglass

@pparent if you post the output of clickable review I should be able to add an exception to let you upload the qt6 app.

kugiigi

@pparent Interesting that click review checks that

pparent

@bhdouglass

clickable review --arch arm64
v8.7.0 of clickable is available, update to get the latest features and improvements!
Cached container is outdated
Running review on /home/pparent/git/My-Ubport-apps/touchpiano/build/aarch64-linux-gnu/app/touchpiano.pparent_0.1.2_arm64.click
Errors
------
 - functional:qt_version_framework
        Unsupported `6.8` version of Qt used: lib/aarch64-linux-gnu/qt6/plugins/platforminputcontexts/libcomposeplatforminputcontextplugin.so
/home/pparent/git/My-Ubport-apps/touchpiano/build/aarch64-linux-gnu/app/touchpiano.pparent_0.1.2_arm64.click: FAIL
Command exited with non-zero exit status 2, see above for details. This is most likely not a problem with Clickable.

gpatel-fr

@pparent
yes it may be a generic test that someone does not try to use a library not included in UT, and not a security check. Here it is:

https://gitlab.com/clickable/click-reviewers-tools/-/blame/master/clickreviews/cr_functional.py?ref_type=heads#L507

Here is the initial goal of this code:
https://gitlab.com/clickable/click-reviewers-tools/-/commit/3d08cd4623c468955016b3f42c0a4bf1ae6a72fb

so maybe it's a generic policy to forbid bundling the whole of QT with your click, or it's a collateral damage of an unrelated hack to solve a specific problem that is now non longer relevant.
Anyway, it seems that bundling the whole of QT in a click is not supported by the automated tool and MorphBrowser QT6 certainly fails it but was allowed because the UT devs believe (wrongly of course) that showing off the new QT6 stuff in the flagship app was more important that playing piano with your,phone

bhdouglass

@pparent I've added the exception, you should be able to upload your click now!

@gpatel-fr feel free to propose a change on the click-reviewers-tools repo.

pparent

@bhdouglass

Ok thank's a lot it worked!

https://open-store.io/app/touchpiano.pparent

I promise I will use Qt6/Qml6 very sparingly, until the library is available inside the OS. In the mean time this app can serve as a demonstration Qml6 app.

Ps: But what might be usefull is to start building a a Qt6 version of Whatsweb, that is currently broken.