On 22/11/13 09:55, David Faure wrote: > On Wednesday 13 November 2013 11:16:24 Alex Merry wrote: >> Alternatively, if the app implements D-Bus Activation, the client can >> pass the desktop startup notification ID via the D-Bus call. The >> application still has to remove it. > > I think most developer would rather not have to deal with startup > notification. I know I considered it a black box for years (even though now > that I know more about it, I realize it's quite simple). > >> The other option, I guess, would be to put this in the API of >> KDBusService: allow the application to set the startup notification ID >> in the constructor, and send it out with the signals. > > I'm not sure what this would look like exactly?
Just an extra argument everywhere, probably a QByteArray. This would conflict with your comment about developers not wanting to deal with it, though. >> Or just ignore it and have no support for startup notifications in >> Unique applications. > > Let's postpone the issue for 4 or 5 months. There's rumours of another > freedesktop meeting, I can get a spec for DBus-based startup notification > sorted out there. I know the glib/gnome people are very much in favour of it, > the Qt/KDE developers looking at wayland are too, so we can move this forward > rather than adding API or dependencies to kdbusaddons that we'll regret later > on. > If we release KF5 and some apps using it before that (which I kind of doubt), > then the workaround is indeed to disable startup notifications for unique > apps > meanwhile (one line in the .desktop file). OK, seems sensible. One thing I'd like to see in this new spec, then, is a way of saying (in the desktop file) "I support the D-Bus version but not the X version", in such a way that old DEs will read it as "I don't support startup notification at all". Alex _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel