Jan Grulich
Jan Grulich
You can mark KDE runtime as done. See https://github.com/KDE/flatpak-kde-runtime/commit/f41edbbb756418d9ea3cc5065e27073aeaeaadbb
Support for this portal will need to be implemented in both Qt and KDE Frameworks. There are applications using QSystemTrayIcon API from Qt, which uses tray implementation based on Qt...
Both basically do the same, just KStatusNotifierItem is a library, or a class from a library, allowing to apps use SNI without doing all the DBus work and knowing the...
Qt's only API for system tray is in QSystemTrayIcon and this will internally use QDBusTrayIcon, or Window system tray or Mac OS system tray, this all depends on platform theme,...
Also, should there be some sanity checks, like only accept the path with the `file://` scheme (or not?) and mention it in the docs? It's always passed like that in...
> > Also, should there be some sanity checks, like only accept the path with the `file://` scheme (or not?) > > You just pass the ID, not the path....
Can you please squash your commits into one?
> So, we are not going for extended file attributes then? Would be nice to have some rationale for why this path has been chosen. I'm worrying a bit about...
> > Maybe a stupid question as this is something I know nothing about. Wouldn't extended file attributes as proposed in the original bug be GIO specific? > > No,...
> One could write code to read the extended attribute just like they could write code to call the portal. There is no need to wait for GIO or anything...