There isn't a standard solution for this. We had the same issue, and
ended up writing a simple template language for the gadget specs that
have the URL substituted by the server providing the gadget.
On Mar 13, 9:54 am, Ziling Zhao wrote:
> It's more like we're writing gadgets that communicate wi
In the and elements in your gadget spec, add the
attribute param_location="uri-query".
There's more detailed documentation at
http://code.google.com/apis/gadgets/docs/oauth.html#ModulePrefs
On Oct 15, 6:48 am, "f.kowal" wrote:
> Hi,
>
> I am developing an oauth gadget, but my hosting doesn't
opment forum at
http://forums.atlassian.com/forum.jspa?forumID=100
Cheers,
Tim Moore
Developer, Atlassian Integration Team
On Sep 30, 3:26 pm, Pablo Fernandez
wrote:
> Hi,
>
> I've heard that JIRA now supports OpenSocial API.
>
> I checked the docs but they were of little help, I cant seem to
On Jun 30, 1:24 pm, "Mark W." wrote:
> Doesn't it make sense then to make sure Shindig and the spec are in
> sync here? If what's in shindig is the most practical way, then let's
> line the spec up with it. If not, let's introduce some option in
> shindig to ensure the portability of the gadgets.
I agree with you, but it seems that the Shindig developers think the
value returned by getString should be escaped. They interpret the
spec as requiring this behavior (though I don't understand how they
read it that way... as far as I can tell, the spec doesn't say
anything about it). The reason
I don't think there's any way to be notified when the save button is
clicked, but I wonder why you need to store the lat and lng in user
prefs at all. Can't you just calculate them dynamically from the city
& zip code whenever you need to use them?
On Jun 27, 7:38 am, jef wrote:
> Hi,
>
> I hav
The UI used in the sample container shipped with Shindig is only an
example and is probably not what you want to use in a production
application. It actually relies on iGoogle's implementation, loading
an external script from gmodules.com and storing saved pref values
in
cookies. Because it's rely
I think you'll want to implement an OAuth client. There's kind of a
lot to it, but you can get started reading http://oauth.net/ for an
overview of how it works,
http://www.opensocial.org/page/sharing-and-accessing-social
for an overview of how it works with OpenSocial, and
http://wiki.opensocial
On Mar 6, 12:10 pm, mick80 wrote:
> But then my concern is - how would the end users be able to see the
> app since most of them won't be iGoogle developers
Right. You're going to have to wait for Google to launch this to the
public, or tell your users to sign up for the sandbox, or write a
Did you sign up for the iGoogle Developer Sandbox?
http://code.google.com/apis/igoogle/docs/gs.html
The generally-available version of iGoogle does not yet fully support
OpenSocial.
-- Tim
On Mar 4, 8:52 am, mick80 wrote:
> Hi Friends,
> I made a open social complaint app and it works fine in
I don't have any definitive information, but it's often the case that
Google Apps for your domain gets features later than standard Gmail
users.
On Mar 3, 1:14 am, String wrote:
> Following on from the blog announcement of GMail as an OS container
> (http://opensocialapis.blogspot.com/2009/02/gm
http://www.opensocial.org/page/building-an-opensocial
On Mar 2, 5:09 pm, "verhe...@live.co.uk" wrote:
> Hello im building a social network, how would I implement the open
> social API into my network so users can add apps to there profiles and
> create apps?
>
> Please get back to me asap.
>
> T
We had some good luck modifying the client found here:
http://www.zentus.com/js/xmlrpc.js.html
Our modified version is at:
http://labs.atlassian.com/svn/FEDEXX/trunk/atlassian.gadgets.xmlrpc.js
You'd probably want to take the alert statement out of the top :-) and
maybe change the namespace.
Ho
13 matches
Mail list logo
