On 6 December 2012 13:34, Franklin, Matthew B. <[email protected]> wrote:
> >-----Original Message----- > >From: Ross Gardler [mailto:[email protected]] > >Sent: Thursday, December 06, 2012 5:54 AM > >To: dev > >Subject: Host Navigation API > > > >Does it make sense to implement a feature that provides an API to allow a > >widget to instruct a host platform to take some navigation action? Does > >such an API already exist? > > I don't know about in W3C widgets; but this pattern is very common in > OpenSocial Gadgets. OpenSoical has a whole RPC layer that it uses to > marshal requests between the widget and its container. In my desire to see > OpenSocial gadget functionality align more with W3C, I could definitely > envision the case where you would want to start to include this capability > in W3C widgets. > I should have thought to look at OpenSocial. >My secondary question is whether this is something that should be done here > >in Wookie or whether this is out of scope. I'm doing the work over on > >GItHub at the moment for a specific project but it seems to me like this > >might be more broadly applicable. > > It would be interesting to see if we couldn't just use some of the same > features from Shindig to make this happen in Wookie Widgets. > > My own interest is in the API specification rather than a Wookie specific implementation of that API. I need to do this, in the first instance, in a Windows 8 RT app that hosts Widgets. So I'm unlikely to contribute to embedding this feature in Wookie, but I would be happy to provide a reference implementation as part of the C# Connector framework if appropriate. If I were able to keep the API compatible with anything Shindig then it would be easier for others to implement the same feature in Java. Ross -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
