committed

Some background about this, and a possible word of warning for those setting up from scratch. Shindig can be installed in two ways, either setting it up at a specific path (foo.bar/shindig/php/gadgets/ifr), or by setting up a vhost to point to the right location (foo.bar/gadgets/ifr). It appears the shindig devs do almost everything from the latter setup, as there are a few less documented files you need to change to get the former set up.

In general, after setting up shindig both ways, adding the vhost was much, much easier and I've had far less problems when going this route. If this is an option, I would really encourage it. However, setting this up in this way breaks the JS includes. I'm not sure the best way to include this patch, should shindig_integrator be aware of how shindig is being accessed? In any case, this will fix the JS problems that will arise if you use this method, however, it still assumes 'shindig' as the install point. To make this completely independent, it should include by url?

Index: shindig_integrator.module
===================================================================
RCS file: /cvs/drupal-contrib/contributions/modules/ShindigIntegrator/shindig_integrator/shindig_integrator.module,v
retrieving revision 1.2.2.2
697,699c697
<   drupal_add_js($path ."/shindig/features/core/util.js?c=1");
<   drupal_add_js($path ."/shindig/features/core/json.js?c=1");
<   drupal_add_js($path ."/shindig/features/rpc/rpc.js?c=1");
---
>   drupal_add_js($js_path .'/gadgets/js/rpc.js?c=1');

Thanks.