I've seen this mentioned a few places but couldn't find an official
request for it, so here is a request to be able to supply a target
owner's ID in the requestNavigateTo function.
Currently, opensocial.requestNavigateTo() redirects the viewer to the
current owner's context.
There are certain use cases where linking to another user's context
would be useful (e.g. "View my friend's application canvas", "Redirect
the page to another user's profile") which are not possible with the
current API.
The requested feature is an additional parameter that may be passed to
requestNavigateTo() which accepts a user's ID number. When the
function is called with this parameter, the supplied user's context is
given as the owner.
<api.kur...@google.com> wrote:
> I've seen this mentioned a few places but couldn't find an official
> request for it, so here is a request to be able to supply a target
> owner's ID in the requestNavigateTo function.
> Currently, opensocial.requestNavigateTo() redirects the viewer to the
> current owner's context.
> There are certain use cases where linking to another user's context
> would be useful (e.g. "View my friend's application canvas", "Redirect
> the page to another user's profile") which are not possible with the
> current API.
> The requested feature is an additional parameter that may be passed to
> requestNavigateTo() which accepts a user's ID number. When the
> function is called with this parameter, the supplied user's context is
> given as the owner.
> On Apr 14, 10:26 am, "Arne Roomann-Kurrik (Google)" > <api.kur...@google.com> wrote: > > I've seen this mentioned a few places but couldn't find an official > > request for it, so here is a request to be able to supply a target > > owner's ID in the requestNavigateTo function.
> > Currently, opensocial.requestNavigateTo() redirects the viewer to the > > current owner's context.
> > There are certain use cases where linking to another user's context > > would be useful (e.g. "View my friend's application canvas", "Redirect > > the page to another user's profile") which are not possible with the > > current API.
> > The requested feature is an additional parameter that may be passed to > > requestNavigateTo() which accepts a user's ID number. When the > > function is called with this parameter, the supplied user's context is > > given as the owner.
> On Mon, Apr 14, 2008 at 10:29 AM, fern...@gmail.com <fern...@gmail.com> wrote:
>> +1
>> On Apr 14, 10:26 am, "Arne Roomann-Kurrik (Google)" >> <api.kur...@google.com> wrote: >>> > I've seen this mentioned a few places but couldn't find an official >>> > request for it, so here is a request to be able to supply a target >>> > owner's ID in the requestNavigateTo function.
>>> > Currently, opensocial.requestNavigateTo() redirects the viewer to the >>> > current owner's context.
>>> > There are certain use cases where linking to another user's context >>> > would be useful (e.g. "View my friend's application canvas", "Redirect >>> > the page to another user's profile") which are not possible with the >>> > current API.
>>> > The requested feature is an additional parameter that may be passed to >>> > requestNavigateTo() which accepts a user's ID number. When the >>> > function is called with this parameter, the supplied user's context is >>> > given as the owner.
> On 4/14/08 12:00 PM, "Louis Ryan" <lr...@google.com> wrote:
>> +1
>> On Mon, Apr 14, 2008 at 10:29 AM, fern...@gmail.com <fern...@gmail.com> wrote: >>> +1
>>> On Apr 14, 10:26 am, "Arne Roomann-Kurrik (Google)" >>> <api.kur...@google.com> wrote: >>>>> I've seen this mentioned a few places but couldn't find an official >>>>> request for it, so here is a request to be able to supply a target >>>>> owner's ID in the requestNavigateTo function.
>>>>> Currently, opensocial.requestNavigateTo() redirects the viewer to the >>>>> current owner's context.
>>>>> There are certain use cases where linking to another user's context >>>>> would be useful (e.g. "View my friend's application canvas", "Redirect >>>>> the page to another user's profile") which are not possible with the >>>>> current API.
>>>>> The requested feature is an additional parameter that may be passed to >>>>> requestNavigateTo() which accepts a user's ID number. When the >>>>> function is called with this parameter, the supplied user's context is >>>>> given as the owner.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
[mailto:opensocial-and-gadgets-spec@googlegroups.com] On Behalf Of Arne Roomann-Kurrik (Google) Sent: Monday, April 14, 2008 10:26 AM To: OpenSocial and Gadgets Specification Discussion Subject: Target OWNER parameter in requestNavigateTo
I've seen this mentioned a few places but couldn't find an official request for it, so here is a request to be able to supply a target owner's ID in the requestNavigateTo function.
Currently, opensocial.requestNavigateTo() redirects the viewer to the current owner's context.
There are certain use cases where linking to another user's context would be useful (e.g. "View my friend's application canvas", "Redirect the page to another user's profile") which are not possible with the current API.
The requested feature is an additional parameter that may be passed to requestNavigateTo() which accepts a user's ID number. When the function is called with this parameter, the supplied user's context is given as the owner.
Well this is overwhelmingly popular! I believe the corresponding spec change would be like this:
* @param {gadgets.views.View} view The view to navigate to * @param {Map.<String, String>} opt_params Parameters to pass to the * gadget after it has been navigated to on the surface * @param {String} opt_ownerId The id of the owner of the page to navigate to. * Defaults to the current owner. */ gadgets.views.requestNavigateTo = function(view, opt_params, opt_ownerId) {};
This is considered approved (unless of course I screwed up the spec change). Thanks.
On Mon, Apr 14, 2008 at 11:27 PM, Amar Gandhi <am...@google.com> wrote:
> +1.
> -----Original Message----- > From: opensocial-and-gadgets-spec@googlegroups.com > [mailto:opensocial-and-gadgets-spec@googlegroups.com] On Behalf Of Arne > Roomann-Kurrik (Google) > Sent: Monday, April 14, 2008 10:26 AM > To: OpenSocial and Gadgets Specification Discussion > Subject: Target OWNER parameter in requestNavigateTo
> I've seen this mentioned a few places but couldn't find an official request > for it, so here is a request to be able to supply a target owner's ID in > the > requestNavigateTo function.
> Currently, opensocial.requestNavigateTo() redirects the viewer to the > current owner's context.
> There are certain use cases where linking to another user's context would > be > useful (e.g. "View my friend's application canvas", "Redirect the page to > another user's profile") which are not possible with the current API.
> The requested feature is an additional parameter that may be passed to > requestNavigateTo() which accepts a user's ID number. When the function is > called with this parameter, the supplied user's context is given as the > owner.
> Well this is overwhelmingly popular!
> I believe the corresponding spec change would be like this:
> * @param {gadgets.views.View} view The view to navigate to
> * @param {Map.<String, String>} opt_params Parameters to pass to the
> * gadget after it has been navigated to on the surface
> * @param {String} opt_ownerId The id of the owner of the page to navigate
> to.
> * Defaults to the current owner.
> */
> gadgets.views.requestNavigateTo = function(view, opt_params, opt_ownerId)
> {};
> This is considered approved (unless of course I screwed up the spec change).
> Thanks.
> > -----Original Message-----
> > From: opensocial-and-gadgets-spec@googlegroups.com
> > [mailto:opensocial-and-gadgets-spec@googlegroups.com] On Behalf Of Arne
> > Roomann-Kurrik (Google)
> > Sent: Monday, April 14, 2008 10:26 AM
> > To: OpenSocial and Gadgets Specification Discussion
> > Subject: Target OWNER parameter in requestNavigateTo
> > I've seen this mentioned a few places but couldn't find an official request
> > for it, so here is a request to be able to supply a target owner's ID in
> > the
> > requestNavigateTo function.
> > Currently, opensocial.requestNavigateTo() redirects the viewer to the
> > current owner's context.
> > There are certain use cases where linking to another user's context would
> > be
> > useful (e.g. "View my friend's application canvas", "Redirect the page to
> > another user's profile") which are not possible with the current API.
> > The requested feature is an additional parameter that may be passed to
> > requestNavigateTo() which accepts a user's ID number. When the function is
> > called with this parameter, the supplied user's context is given as the
> > owner.