Comment on attachment 91532 [details] [review]
desktop entry spec: Add support for Implements=

Review of attachment 91532 [details] [review]:
-----------------------------------------------------------------

::: desktop-entry/desktop-entry-spec.xml
@@ +896,5 @@
> +      The <varname>Implements</varname> key can be used to declare one or more interfaces that a desktop file
> +      implements.
> +    </para>
> +    <para>
> +      Each interface name must follow the rules used for D-Bus interface names, but other than they, they have

Typo in "other than they"

@@ +902,5 @@
> +      application implements that D-Bus interface or even that such a D-Bus interface exists.  It is entirely up
> +      to the entity who defined a particular interface to define what it means to implement it.
> +    </para>
> +    <para>
> +      Although it is entirely up to you to decide what a given interface name means, here are some recommended

In general, we don't use "you" in the spec, iirc. It's actually unclear who this would be: people writing desktop files or people reading desktop files?

Comment on attachment 91532 [details] [review]
desktop entry spec: Add support for Implements=

This is missing something very important: where are listed the available interfaces that can be used here?

Maybe just a link to some freedesktop wiki page with zero or one interface as a starting point, but this is definitely needed, for anyone reading this spec to be able to find out the available interfaces or where to add the one they want to define so others can know about it.

(In reply to comment #2)
> Comment on attachment 91532 [details] [review] [review]
> desktop entry spec: Add support for Implements=
> 
> This is missing something very important: where are listed the available
> interfaces that can be used here?

I've been talking to Alex Fiestas to implement an org.kde.intents.Camera.TakePicture interface of his choosing in kamoso, as a starting point (I'd love to demo that at fosdem though we're tight on time for that).

PCMan mentioned this is all a very solid alternative to the current various hacky ways we have of displaying file picker dialogs: A "file picker" app can be installed (eg as part of the file manager or on its own) and support org.freedesktop.intents.FileManager.FilePickerDialog or something similar. This would allow for a shared, integrated file picker between DEs.

After meeting up with Ryan at FOSDEM we discussed the potential use cases.

Ryan wants a more generic "Implements", which would be able to contain any dbus-like addresses for anything the app implements.

Intents, as a concept, would reuse the Implements key (as the app would implement the intents).

So it could look something like this:

Name=MediaUploader
Implements=org.freedesktop.intents.ShareFile

[Intent org.freedesktop.intents.ShareFile]
MimeType=image/png;

(In reply to comment #4)
> After meeting up with Ryan at FOSDEM we discussed the potential use cases.
> 
> Ryan wants a more generic "Implements", which would be able to contain any
> dbus-like addresses for anything the app implements.
> 
> Intents, as a concept, would reuse the Implements key (as the app would
> implement the intents).
> 
> So it could look something like this:
> 
> Name=MediaUploader
> Implements=org.freedesktop.intents.ShareFile
> 
> [Intent org.freedesktop.intents.ShareFile]
> MimeType=image/png;

Note that this also implies we don't need intents examples (like android has) for this particular bug.

I'm OK with this; David?

Pushed.