On Thu, May 22, 2008 at 3:41 PM, Chris Chabot <[EMAIL PROTECTED]> wrote: > Been debugging some popular gadgets yesterday and today to make them work > with php shindig / partuza.chabotc.com to demo them at the upcoming Google > IO event. > > iLike is already working (big thanks to Nat @ iLike for his time and effort > on that!), however with the guys from rockyou.com we ran into a snag... > > The snag being that the prototype.js they included caused this error message > (before any code was even executed): > "Event.Methods[name].methodize is not a function" > > After some head scratching and random guesses, it turned out that it was the > inclusion of caja.js that broke it .. > > Now i don't have server sided cajoling in php shindig, i had enableCaja : > false in container.js, but the shear fact of including caja.js broke it. > > The work-around to get to a working demo platform was to edit > opensocial-0.7/features.xml and remove the caja feature dependency. > > So .. it seems that having the caja dependency in the opensocial feature.xml > breaks apps .. is this something the live containers (orkut, hi5) had to > work around too, or is caja.js being included there too? And if so, do > gadgets that include prototype.js work there?
To the best of my knowledge, nobody is using caja in production. Orkut certainly isn't. We plan on enabling it for google containers sometime late this summer, once Mike Samuel tells us it's ready. > > I could easily make a work around in php shindig that i blacklist the caja > feature from loading, and thus 'fixing' this situation, but I'm curious if > it's a php shindig only problem or happened with other deployments too. > > -- Chris > >
