Thanks Stanton. I agree that Rave is probably an easier starting place for what you are wanting to accomplish. Many of the original codebases that were the pre-cursors to Rave were built to provide iGoogle like functionality to their users. As Stanton points out, Rave uses Shindig to render OpenSocial (Google) Gadgets and provides features for managing those gadgets in pages. I have included direct answers to your questions inline.
>-----Original Message----- >From: Stanton Sievers [mailto:[email protected]] >Sent: Sunday, July 29, 2012 12:39 PM >To: [email protected]; [email protected] >Subject: Re: Please point out any caveats before I begin > >I don't think there are any major roadblocks you would hit with Shindig. >However, I think Rave may be the better tool to use - it's backed by >Shindig under the covers anyway. > >I've cc'd the rave use group as well to get their opinion on your specific >questions. > >Best regards, >-Stanton > On Jul 29, 2012 4:48 AM, "any bloke" <[email protected]> wrote: > >> I am making a public facing website and I am *very* interested in >> using Shindig (possibly together with Apache Rave) to allow public >> users to add Google gadgets to their "start page" in a manner very >> similar to iGoogle. >> >> I'm going to be facing a steep learning curve to reach my goal, and >> I'd just hate to be days or weeks into it only to hit a critical >> gotcha that scuttles the entire plan. So I hope you don't mind my >> attempt to pick your collective brains. >> >> So I was wondering... >> >> * Do you know of any reason why the vast majority of gadgets would >> not run in Shindig? Anything OpenSocial compliant should run without issue in Rave or Shindig. We haven't come across many in the iGoogle store that have not worked. >> >> * Do you know of any category or type of gadgets that will not? >> (Excluding those that depend on secured Google services, like Gmail) The Gmail one used to not work due to a proprietary authentication system. OpenSocial fully supports OAuth 1.0a (1 & 2 legged) and OAuth 2.0 (authorization code); which means that any service that supports OAuth should be easily accessed via a gadget. >> >> * Do you know of any problems that will prevent me from implementing >> an iGoogle like experience for my users? >> As with any implementation, you will face challenges; but, nothing that is a blocker IMO. >> * Do you have any other warnings or advice I should consider before >> beginning? Download the software and play around with it :). Rave has bundled tomcat binaries that include the Rave, Shindig & Wookie wars. That is a good way to get your feet wet. >> >> I understand that Shindig is about more than gadgets, which will be of >> great additional benefit down the line, but at this time I can only >> justify this project as a means to the end goal of hosting gadgets for >> my website users. >> >> If this goal is workable in the short term, I hope that I will be >> capable of giving back to the community in the medium to long term >> with submissions to the code base. I will be new to open source >> development, but I look forward to a chance to finally get involved. Like all Apache project, Rave & Shindig appreciate patches, contributions to discussions and submission of issues. Let us know how it goes and don't be afraid to ask questions.
