On Nov 29, 3:59 pm, Chris wrote: > This sounds great, but I thought the whole point of OpenSocial was to > take care of these types of issues for us? Yes and no, First, reality is that containers are implemented differently and during the process of their changes it will be easier to keep changing one common js class than for each developer to watch if his applications are not broken during this process. Second, also when (and if) containers will provide stable and similar functionality, I think it could be useful to use prototype.lite.js library. Only problem that it is adding some overhead and is taking additional resources and therefore could be integrated with other OS libraries for efficiency. PS. isQwner function is available for hi5 today, but not working correctly. Cheers.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial API Definition" 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-api?hl=en -~----------~----~----~----~------~----~------~--~---
