New ConverseJS (XMPP) app with broken source links?

pparent

@wilson101 said in New ConverseJS (XMPP) app with broken source links?:

Where should I put helper.send("Hello world") ? in the main.qml?

Sorry the documentation was not up to date
It's not helper.send("Hello world") but helper.showNotificationMessage("title","Hello world")

If your webapp emits desktop notifications you can add to your webview

onPresentNotification: (notification) => {
               helper.showNotificationMessage(notification.title, notification.message);
        }

Otherwise you would need to send a message in js through console.log and then get it in QML with:

onJavaScriptConsoleMessage: function(level, message, line, sourceId) {

Or you can simply make the app emit desktop notifications which is easy in js.

poVoq

@pparent said in New ConverseJS (XMPP) app with broken source links?:

That being said XMMP protocol might support real push notifications, i.e the server calls a endpoint ( here https://push.ubports.com/notify ) when a new message arrives, and this allows to wake up the phone and display notification. This would be more ideal as the app would not need to run in background to get the notifications.

Yes, but it would require modifying a module on the server, so it will not work with most XMPP servers out there.

The probably better alternative would be for the app developer to run a push relay that pretends to be a FCM relay but pushes to the UBports server instead. Not sure how difficult it would be to modify existing software for that though.

pparent

@poVoq

Standard XMMP protocol does not allow to register a custom push server? If so it was poorly designed for a federated protocol...

wilson101

I'm wondering why the sound notifications don't work even if I use the tweak tool and prevent app suspension. On my computers browser works. On the app don't work.

wilson101

Ok I fixed that now sound notifications are working, but we need to make the app not suspend from the tweak tool if we want to get notifications on locked screen.

pparent

@wilson101

Congrats , thought it might not be ideal to let your app emit notification sounds in background, because users could want their phone to be in mute mode, and only vibrate (+ if you don't hear the notification you cannot know if there was one later).

Ideally you could make notifications real UT notifications as I did in whatsweb:

https://github.com/alefnode/ubports-apps/pull/44/commits

wilson101

@pparent It's not ideal for sure. But QML is to confusing for me to be able to implement the push notifications properly with the js code of conversejs. If you have any ideas how to do it exactly I will appreciate it.

pparent

@wilson101

It's basically doing the exact same thing I did in this pull request:

https://github.com/alefnode/ubports-apps/pull/44/commits

Although you can do something much simpler because, to make sure I don't miss a notification I've taken into account 3 sources: desktop notifications, title change, and sound. The first one may be enough in your case.

wilson101

@pparent desktop notifications are enabled in covnerejs by default, but I don't know how to enable them in QML to be able to interact with your module.

pparent

@wilson101

Also make sure to allow your webview to receive desktop notifications in the first place:

onFeaturePermissionRequested: {
       grantFeaturePermission(securityOrigin, feature, true);
       }

pparent

@wilson101 said in New ConverseJS (XMPP) app with broken source links?:

@pparent desktop notifications are enabled in covnerejs by default, but I don't know how to enable them in QML to be able to interact with your module.

Well first you add to your webview

onFeaturePermissionRequested: {
       grantFeaturePermission(securityOrigin, feature, true);
       }

Then in the profile of the webview:

profile:  WebEngineProfile {
......

         onPresentNotification: (notification) => {
                helper.showNotificationMessage(notification.title, notification.message);
         }
         
    .......
       
       }//End WebEngineProfile

It should be pretty straight forward.

wilson101

@pparent I have a question about onFeaturePermissionRequested: {
grantFeaturePermission(securityOrigin, feature, true);
}
should I replace feature with notification or whatever name it has in qml or leave it like that ?

wilson101

I'm trying this now onFeaturePermissionRequested: {
grantFeaturePermission("http://127.0.0.1:9090/index.html", Notifications, true);
}

I saw the examples here https://doc.qt.io/qt-6/qml-qtwebengine-webengineview-obsolete.html#featurePermissionRequested-signal

wilson101

I'm doing something wrong the app froze

pparent

@wilson101 said in New ConverseJS (XMPP) app with broken source links?:

should I replace feature with notification or whatever name it has in qml or leave it like that ?

Yes you can allow only notifications permissions, but if I were you I would see that once you get notifications working in the first place.

Normally what you want to do would be something like that:

onFeaturePermissionRequested: function(securityOrigin, feature) {
        if (feature === WebEngineView.Notifications) {
            grantFeaturePermission(securityOrigin, feature, true); 
        } else {
            grantFeaturePermission(securityOrigin, feature, false); 
        }
    }

wilson101

@pparent The problem now is that I can't import your code. This is main.qml https://pastebin.com/raw/kt9cpWBz I get :/qml/Main.qml:37 NotificationHelper is not a type