Hi Henry, Thanks. In order to clarify our intentions, we are looking to provide a site very similar to iGoogle with the majority of features and benefits it provides. Our intention is for users to be able to "switch over" from iGoogle prior to the November 1st deadline - not long now!
Ideally this means we want to provide Google's own range of gadgets, fully operational, on our site. We do not intend to host gadgets per se. Furthermore, we are not really looking to re-write the vast majority of Google gadgets as the intention is to focus on site features and for gadgets to be written and supported by the various third parties (although we will be providing some bespoke gadgets of our own). Therefore it is in our interests to get the Google authored gadgets working on our site where possible. Looking at the replies from yourself, Ryan/Stanton et al it appears we are going to struggle to achieve this if Google are using internal magic to get them to function correctly? Kind regards, Darren ---------------------------------------- From: "Henry Saputra" <henry.sapu...@gmail.com> Sent: 04 October 2013 01:30 To: "dev@shindig.apache.org" <dev@shindig.apache.org>, "Darren Bond" <db...@globalcad.com> Subject: Re: Data Persistence of Google Gadgets (e.g. TODO List) Hi Darren, It is good to see you guys moving further with Apache Shindig as OpenSocial container. Yeah, it used to work very well with Apache Shindig trunk =( - Henry On Wed, Oct 2, 2013 at 4:43 AM, Darren Bond <db...@globalcad.com> wrote: > Thanks Ryan/Matt, Given this is a Google gadget, I don’t think we have any > chance of reaching out to the OAuth provider. It’s a shame we can’t get it to > work as it appears to be used in many examples of how to configure Shindig. > Kind regards, Darren
