+1 There have definitely been some challenges and a learning curve, but working with Shindig has been a great experience in my opinion. The choice of technologies in Shindig has provided a pretty flexible platform and in a lot of cases for me a great example on how to use those technologies. Shindig's use of Maven, for example, is more robust than any examples I could find out on the net for a complex project setup. It also allows Shindig to be integrated into the application I am working on while still maintaining separation. Shindig is one of the more robust and full featured open source applications I have seen.
On Mar 6, 12:30 am, Randgalt <[email protected]> wrote: > +1 > > So, I'll start with my own experience. I've been tasked with > implementing an OpenSocial container for our application. I've been > working on this since December. Early on, I was told that Shindig was > the way to go instead of rolling my own. So far, it has been one of > the most unpleasant experiences of my career. There's no documentation > whatsoever, it's written as a self-contained web application and not a > code library, it uses copious new technologies (DI, maven, etc.) that > make code discovery nearly impossible, major important points of > integration are hard coded into .js files (URLs, etc.) - I could go on > and on. > > Am I the only one suffering with this thing? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Implementing OpenSocial Containers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/opensocial-container?hl=en -~----------~----~----~----~------~----~------~--~---
