State and plans for LibSnoreToast

[Hannah von Reth]

Hi Albert,

On 30/03/2019 18:01, Albert Vaca Cintora wrote:
> Hi Hannah (+ KDE on Windows mailing list),
>
> We would like to have a GSOC project this year to improve KDE Connect
> on Windows. One of the main items for this GSOC is to integrate with
> Windows' notifications API.
I'm aware he already contacted me :)
> Since you have been working on it via SnoreToast and LibSnoreToast, I
> would like to get a few pointers on what to do from you.
>
>  From what I know, using the Windows notifications API is not that
> simple: your app needs to be installed with a shortcut in the Start
> Menu for it to work. I think this is the rationale behind having
> SnoreToast: SnoreToast can be in the Start Menu and all apps just
> create notifications through it. Correct me if I'm wrong.
>
> I've seen now, from one of our student's proposals, that there is also
> LibSnoreToast. I guess this removes the need of having SnoreToast
> running alongside your app, which is much better. Is this the case?
> Also, is this library in a usable state?

There wasn't but I'm working on libifying it.

SnoreToast.exe also supported custom shortcuts, it does not run along 
side but you call it for each notification.

The api is msvc only so it is not possible to build the lib with mingw, 
while it would still be possible to call a external snoretoast.exe .

> Regarding LibSnoreToast: is it going to be a backend for
> KNotifications, or is it something that should be used instead of
> KNotifications? Ideally, I would love to be able to just use
> KNotifications and get native Windows notifications. Is this possible,
> or in your roadmap? Otherwise, maybe our GSOC student can help you on
> this :)
He proposed to integrate it in kdeconnect and later in knotifications, 
maybe a direct approach would be better.
> And last, a technical question: Given that LibSnoreToast is a library,
> how do you solve the problem of the app having to be in the Start
> Menu? Do you just print a warning in debug builds saying that
> notifications won't work unless the developer does this part? I think
> that would be enough, and wouldn't require any change from the current
> KNotifications API, but I don't know if this is your solution.

As before you still need a special shortcut, I'd recommend to use 
Snroetoast.exe during the setup.

I could make the capability to install shortcuts available in the lib 
but... I'm not sure yet.

If no shortcut is registered libsnoretoast will report an error.

> Sorry for making so many questions, and thanks a lot for your time!
> Hopefully this GSOC project can benefit the entire KDE on Windows
> ecosystem :)
>
> Albert


Cheers,


Hannah