<div dir="ltr"><div><div><div><div><div>A protocol is simply a semi-standard way of using an application.<br><br></div>For instance, when you set the EDITOR environment variable, the expectation is that the command in EDITOR will accept at zero or one filenames after it.<br>
<br></div>So: `$EDITOR my_file.txt`<br><br></div>I'd consider that a "protocol". It's undocumented and mostly ad-hoc (UNIX philosophy at its finest), but lots of programs support launching `$EDITOR`, and lots of programs support being set as `$EDITOR`.<br>
<br></div>If I make a "default browser selector" widget, there better be a way of telling the browser how to launch a specific webpage, since the whole point of a "default browser" is to let me select what happens when I click on a very specific webpage. Yes, web browsers don't *have* to have that functionality, but they shouldn't be able to be selected as a "default browser".<br>
<br>So, I'm skeptical of the value or utility of the user selecting
one of many "IRC Client"s from a list without any guarantee about what
the program even does. So, what's the goal of building a list of IRC Clients? What will the user do with this list that's good for them?<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 7, 2014 at 11:51 AM, Jerome Leclanche <span dir="ltr"><<a href="mailto:adys.wh@gmail.com" target="_blank">adys.wh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, Jan 7, 2014 at 4:00 PM, Jasper St. Pierre <<a href="mailto:jstpierre@mecheye.net">jstpierre@mecheye.net</a>> wrote:<br>
> What's the use case you imagine where the user would want to choose from a<br>
> list of IRC clients, without the list actually able to launch the IRC client<br>
> in question with a specific server/channel?<br>
<br>
</div>We've been through this.<br>
<div class="im"><br>
><br>
> It seems quite backwards to have a way to say "this app supports this<br>
> API/protocol" with the app actually not being able to support that<br>
> API/protocol. If the app wants to announce itself as an IRC client, it needs<br>
> to handle the "I support IRC protocol". Yes, that could mean something<br>
> different from irc: URIs, but if Quassel doesn't support IRC URIs, what<br>
> makes you think it will gain support for your protocol, or why your protocol<br>
> is better than IRC URIs?<br>
<br>
</div>Please do not make assumptions about an app's command line interface.<br>
A web browser can be a web browser without ever accepting http uris as<br>
argument. IM clients themselves are much, much less likely to accept<br>
protocol URIs, especially since some of the protocols they support<br>
simply don't have special URIs, and just because xmpp does doesn't<br>
mean that it makes sense to accept it as a URI.<br>
<br>
Furthermore I have no idea what you mean by "gaining support for my<br>
protocol". You are conflating protocols and URIs.<br>
<br>
J. Leclanche<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
><br>
> On Tue, Jan 7, 2014 at 10:34 AM, Jerome Leclanche <<a href="mailto:adys.wh@gmail.com">adys.wh@gmail.com</a>> wrote:<br>
>><br>
>> On Tue, Jan 7, 2014 at 3:24 PM, Dominique Michel<br>
>> <<a href="mailto:dominique.michel@vtxnet.ch">dominique.michel@vtxnet.ch</a>> wrote:<br>
>> > Le Mon, 6 Jan 2014 15:38:34 +0000,<br>
>> > Jerome Leclanche <<a href="mailto:adys.wh@gmail.com">adys.wh@gmail.com</a>> a écrit :<br>
>> ><br>
>> >> On Mon, Jan 6, 2014 at 1:56 PM, Bastien Nocera <<a href="mailto:hadess@hadess.net">hadess@hadess.net</a>><br>
>> >> wrote:<br>
>> >> > On Mon, 2014-01-06 at 14:48 +0100, David Faure wrote:<br>
>> >> >> On Monday 06 January 2014 14:44:27 Bastien Nocera wrote:<br>
>> >> >> > On Mon, 2014-01-06 at 14:35 +0100, David Faure wrote:<br>
>> >> >> > > On Monday 06 January 2014 14:28:01 Bastien Nocera wrote:<br>
>> >> >> > > > And it's more about services (allow me to pick a photo, or<br>
>> >> >> > > > select a contact) than about full-fledged applications. A<br>
>> >> >> > > > terminal emulator can hardly be thought as providing a<br>
>> >> >> > > > service to other applications, a photo picker provided by<br>
>> >> >> > > > the native photo application would.<br>
>> >> >> > ><br>
>> >> >> > > My point is that both needs (i.e. use cases) exist.<br>
>> >> >> > ><br>
>> >> >> > > I know that "intents" and the use of dbus interfaces is about<br>
>> >> >> > > what you describe.<br>
>> >> >> > ><br>
>> >> >> > > I'm simply pointing out that the other use case (merely<br>
>> >> >> > > starting apps, at most with a url on the command line) exists<br>
>> >> >> > > too, and that I'd like to see a standard solution for it.<br>
>> >> >> ><br>
>> >> >> > The URL would/should have a mime-type associated to it, so you<br>
>> >> >> > can just lookup by mime-type.<br>
>> >> >><br>
>> >> >> "at most" means "sometimes none".<br>
>> >> >><br>
>> >> >> There's no URL and no mimetype involved when listing or starting<br>
>> >> >> - window managers<br>
>> >> >> - terminal emulators<br>
>> >> ><br>
>> >> > Those would be covered by the Implements changes documented by Ryan:<br>
>> >> > <a href="https://bugs.freedesktop.org/show_bug.cgi?id=73317" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=73317</a><br>
>> >> ><br>
>> >> >> - instant messaging apps<br>
>> >> ><br>
>> >> > xmpp, and irc schemes at least, so those are covered by<br>
>> >> > x-scheme-handler/*<br>
>> >> ><br>
>> >> >> - email clients<br>
>> >> ><br>
>> >> > mailto scheme<br>
>> >> ><br>
>> >><br>
>> >> All these are not safe assumptions. Quassel, for example, does not<br>
>> >> support irc: uris.<br>
>> ><br>
>> > Is it not the job of an application, or package manager, to<br>
>> > provide the right mimes type for the application?<br>
>> ><br>
>> > If that mime type does not exist, it must be added.<br>
>> ><br>
>> > Dominique<br>
>> >><br>
>> >> J. Leclanche<br>
>> >> _______________________________________________<br>
>> >> xdg mailing list<br>
>> >> <a href="mailto:xdg@lists.freedesktop.org">xdg@lists.freedesktop.org</a><br>
>> >> <a href="http://lists.freedesktop.org/mailman/listinfo/xdg" target="_blank">http://lists.freedesktop.org/mailman/listinfo/xdg</a><br>
>> > _______________________________________________<br>
>> > xdg mailing list<br>
>> > <a href="mailto:xdg@lists.freedesktop.org">xdg@lists.freedesktop.org</a><br>
>> > <a href="http://lists.freedesktop.org/mailman/listinfo/xdg" target="_blank">http://lists.freedesktop.org/mailman/listinfo/xdg</a><br>
>><br>
>> The association is irrelevant. Quassel does not support being given<br>
>> irc uris. You're welcome to write a patch for every broken app,<br>
>> though.<br>
>><br>
>> J. Leclanche<br>
>> _______________________________________________<br>
>> xdg mailing list<br>
>> <a href="mailto:xdg@lists.freedesktop.org">xdg@lists.freedesktop.org</a><br>
>> <a href="http://lists.freedesktop.org/mailman/listinfo/xdg" target="_blank">http://lists.freedesktop.org/mailman/listinfo/xdg</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Jasper<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br> Jasper<br>
</div>