I like the parameter approach better. Another question along this line:
Are OpenSocial Template Libraries fully implemented within Shindig as it stands now? I haven't been able to get template libraries to show in the client side opensocial.template api. I just pulled down the current trunk this morning. I have been stepping through the code and I can see that my Template Libraries are being read into the TagRegistry, but can't seem to find where the read-in template libraries go after that. -----Original Message----- From: Lev Epshteyn [mailto:[email protected]] Sent: Tuesday, May 05, 2009 11:47 AM To: [email protected] Cc: Adam Winer; Evan Gilbert Subject: Re: Template JS API I'm probably going to be adding functionality to Shindig to control the removal/availability of client-side templating Do you think this should be done via A) Optional opensocial-templates-client feature B) <Param name="client">true|false|{auto}</Param> on opensocial-templates feature - where true requests that client code be left in always, false requests its removal and auto preserves current logic ? >>> We should probably add a feature to Shindig to always enable client-side >>> processing.
