>Along with allowing applications to define more URIs, we'll need to
mediate between them. For instance you register for "http://*facebook.com/*";
and so does the official Facebook app... what to do. I consider figuring
out that as part of the work above. Ideas welcome :-)
I think this is one o
On Wed, 2013-09-18 at 15:38 -0500, Jamie Strandboge wrote:
> On 09/18/2013 01:31 PM, Ted Gould wrote:
> > Folks have been pushing me (rightfully so) to get a little more user
> > friendly
> > documentation out there about the URL Dispatcher. I went ahead and wrote up
> > this Wiki page:
> >
> >
On Wed, 2013-09-18 at 15:58 -0400, Alexandre Abreu wrote:
> It might be a little pedantic, but shouldn't we talk about URI instead
> of URL?
Yeah, that is a little pendantic :-) Perhaps, but I think for most
people they're synonymous.
> Besides that a few questions:
>
> - Is APP_ID going to be
On 09/18/2013 01:31 PM, Ted Gould wrote:
> Hello,
>
> Folks have been pushing me (rightfully so) to get a little more user friendly
> documentation out there about the URL Dispatcher. I went ahead and wrote up
> this Wiki page:
>
> https://wiki.ubuntu.com/URLDispatcher
>
> For those that are lo
Hi Ted,
thanks for that!
It might be a little pedantic, but shouldn't we talk about URI instead of
URL?
Besides that a few questions:
- Is APP_ID going to be used in e.g. the proposed URI
application://$(APP_ID).desktop (why specify the ".desktop" btw?), by that
I mean w/ the version included?
Hello,
Folks have been pushing me (rightfully so) to get a little more user
friendly documentation out there about the URL Dispatcher. I went ahead
and wrote up this Wiki page:
https://wiki.ubuntu.com/URLDispatcher
For those that are looking for the source code for the service it is
here:
http
6 matches
Mail list logo
