Until type=url is formally supported in orkut social gadgets, the
following workaround will allow calling
google.people.requestData from a third party website.
Be aware that this method introduces considerable latency to the
social calls and should not be mistaken for a production-ready
library
You will need the following files:
You will also need to be using Firefox, with Firebug installed and enabled
typeurl.core.js and change the
typeurl.settings.BASE_REMOTE_URL setting to reflect the
server and subdirectory where you will be hosting your gadget.
typeurl.xml and change the script tags
to point where you will be hosting the typeurl.core.js and
typeurl.local.js files.
http://PATH-TO/typeurl.xml?site=http://PATH-TO/remote.html
as an Orkut application. For example,
http://graargh.returnstrue.com/typeurl/typeurl.xml?site=http://graargh.returnstrue.com/typeurl/remote.html
remote.html and represents a type=url gadget
not running on gmodules.com.
remote.html, by using the standard
google.people.requestData function
Examining remote.html will show that aside from the
lines
<script src="typeurl.core.js"></script>
<script src="typeurl.remote.js"></script>
all calls to the social api function as they would with type=html gadgets
Changing the remote.html path
You can change the remote.html path to something else by changing the
querystring that you install your application to. For example,
installing
http://graargh.returnstrue.com/typeurl/typeurl.xml?site=http://graargh.returnstrue.com/typeurl/someotherfile.php
will point to someotherfile.php on your server.
Note: In addition to changing the path parameter, you will also need to
rename remote.callback.html to [new path].callback.html.
For the example above, you need to rename
remote.callback.html to
someotherfile.php.callback.html