Why did you add a BSD close to the makefile ?

In T8905#258273, @ognarb wrote:

I also made a small MR :) https://invent.kde.org/smigaud/kompass/-/merge_requests/2

btw could you add a license file to Kompass? even better make it reuse compliant :)

Randome drive-by comment: Would it make sense to use https://doc.qt.io/qt-5/qcompass.html ?

I also made a small MR :) https://invent.kde.org/smigaud/kompass/-/merge_requests/2

Sure, Thanks a lot for your help !

Thanks, I have done a few commits, is it okay if I do one bulk merge request? The changes are separated into commits.

It's on invent, on this repository
Thanks for your interest !

Cool, thank you for working on it! For the next steps, consider moving the repository to invent.
I have a few comments on the code, but I'll just open a merge request once it's on invent :)

I have a POC available at this address : Kompass
The compiled binary :

I wrote https://invent.kde.org/network/tokodon. Still missing a few things: notifications views and some special events support but many features were implemented.

Is it OK if I claim this project ?

Is it OK if I claim this project ?

I started working on it. I have a small demo app (really rough : https://github.com/Gnu-Bricoleur/Kompass).
There's two major issues right now :

Kasts now works pretty well: https://invent.kde.org/plasma-mobile/kasts

On Tuesday, 17 March 2020 07:46:40 PDT cah fofpai wrote:

cahfofpai added a comment.

There's also https://github.com/err4nt/blabber .

TASK DETAIL

https://phabricator.kde.org/T12814

To: cahfofpai
Cc: cahfofpai, IlyaBizyaev, tfella, ognarb, jackyalcine, muesli,
dkardarakos, Orage, hannahk, frmdstryr, fbampaloukas, emrek, mkraemer,
asghaier, lezsakdomi, tbalzer, PureTryOut, lnj, neofytosk, alexeymin,
jbbgameich, dvasin, jessep, Sergobot, sebas

There's also https://github.com/err4nt/blabber .

Yeah, from my experience working with Rust, wrapping C++ libraries in it isn't too foreign for C++ developers. I was planning on remodelling the GUI logic and KDE bits for ActivityDesk using the same flow that Ikona had tbh.

In T12814#223341, @tfella wrote:

In T12814#223340, @muesli wrote:

Also not opposed to a Kirigami front-end and happy to provide help here. I'm not sure the Go backend is well-suited for the entire KDE infrastructure, though.

Neither is Rust, we're still using it in some applications though, so that should not be a problem i guess?

In T12814#223340, @muesli wrote:

Also not opposed to a Kirigami front-end and happy to provide help here. I'm not sure the Go backend is well-suited for the entire KDE infrastructure, though.

Also not opposed to a Kirigami front-end and happy to provide help here. I'm not sure the Go backend is well-suited for the entire KDE infrastructure, though.

In T12814#223336, @jackyalcine wrote:

I'm open to working on a Kirigami front-end. I leveraged Rust because there's an existing library for Mastodon interoperability.

I'm open to working on a Kirigami front-end. I leveraged Rust because there's an existing library for Mastodon interoperability.

There is already work in multiples Qml/Qt Mastodon appliations:

Rustygator and Kirigator are dead;

@cahfofpai We could probably flatpak https://open-store.io/app/flas.cibersheep, it doesn't seem to use compiled code or anything special.

Maybe we should create an internet radio app instead

Would be interesting to make the startup sound customizable and configurable

A weird idea was to fork VVave (https://invent.kde.org/kde/vvave), the music player, and add functionality to save playback progress to get a simple audio book and podcast player (not a subscriber and downloader) without too many extra efforts.

Some work has already been done:
https://invent.kde.org/jbbgameich/rustygator (quite active project with basic functionality)
https://invent.kde.org/nicolasfella/kirigator (empty repository)

Thank for your interest in working on this. It is not strictly necessary to start with a mockup, but it would probably be useful to work together with the KDE VDG team.
@nicolasfella already created a repository for this (but there doesn't seem to be code yet), so maybe you can work together if you want.

I would like to work on this. Should I build a mockup first?

The existing radio functionality of Qt seems to be deprecated since https://github.com/qt/qtmultimedia/commit/f1648c837b606cbb62972aa98e373ac839883872

Index is a cool thing, I don't think we need anything else

This is probably already implemented in index.
Repository: https://github.com/mauikit/index
Packaging: https://gitlab.com/debian-pm/apps/index

Project to run gPodder QML on Plasma Mobile: https://invent.kde.org/jbbgameich/gpodder-qml
Packaging: https://gitlab.com/debian-pm/apps/gpodder-qml

The QML touch ui for gPodder (https://github.com/gpodder/gpodder-ui-qml) seems to work very well already.
It looks like this (unfortunately I'm missing the required font for the icons on my system):

I started writing the application some month ago, but I'm not sure whether FM Radio even works with the currently supported devices.
Just in case anyone wants to test it, the source code is here: https://gitlab.com/JBBgameich/fm-radio

We should consider using Radio QML Type since it seems that it fits our needs.