We would appreciate a patch for sure but maybe the easiest thing to do before going that path is to see if Google would be willing to open source that JavaScript to Shindig. This would allow you to continue to use you existing container while you look into transitioning to the new common container in Shindig 2.5.
Paul is this something you might be able to help with? On Wed, Jun 12, 2013 at 4:33 AM, Niekerk, C. van (Charl, ICTS) <[email protected]> wrote: > On Tue, Jun 11, 2013 at 11:34:01AM -0700, Henry Saputra wrote: >> This feature should have been removed with the new Shindig's common >> container support under features/container directory. > > The reference to gmodules.com still exists in the shindig-container.js script > in the trunk. > > How do we fix this, and how easy would it be to port this back to Shindig 2.0 > (the version we are using right now)? > > Like I said previously, we are currently looking at solving this with a > separate Java Servlet, so we do have development capacity. > > If there is a better way of doing this, I would like to explore that first > and contribute a patch (if possible). > >> I believe you are trying to provide OpenSocial container for your site? > > Yes, we have an application running in production that provides an OpenSocial > container. > > -- > Charl van Niekerk > ICT Service Centre > University of Twente
