<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
    <channel>
        <title>roomanna.com</title>
        <link>http://roomanna.com/</link>
        <description></description>
        <language>en-US</language>
        <copyright>Copyright 2009</copyright>
        <lastBuildDate>Tue, 04 Aug 2009 11:38:22 -0800</lastBuildDate>
        <generator>http://www.sixapart.com/movabletype/</generator>
        <docs>http://www.rssboard.org/rss-specification</docs>
        
        <item>
            <title>Changes to the validating signed requests algorithm in 0.9</title>
            <description><![CDATA[<p>Last week I ran into a minor issue related to my validating signed request code in the OpenSocial Dev App. A container which had been custom written against the 0.9 spec was sending OAuth messages which were not validating, even though I was certain that I had installed the correct key for the container. After some debugging, I realized that the container was sending a property named <code>xoauth_public_key</code> where I was expecting <code>xoauth_signature_publickey</code>. Consulting the spec, I was amazed to see that the parameter had changed names in this subtle way:</p>

<table class="tabular">
<tr><th>OpenSocial version</th>
<th>Parameter name</th>
</tr>
<tr><td>Before 0.9</td>
<td><code>xoauth_signature_publickey</code></td>
</tr>
<tr><td>0.9 and later</td>
<td><code>xoauth_public_key</code></td>
</tr>
</table>

<p>Since there's no signal indicating which version of the spec a signed request follows, I realized that this change will likely trip up existing app developers once Shindig changes to the new system.</p>

<p>Finding the <a href="https://issues.apache.org/jira/browse/SHINDIG-609">appropriate bug</a> in Shindig's issue tracker, I was happy to see that both parameters will be sent by both Java and PHP Shindig for the time being (at least until we move on to whichever version comes after 0.9). This should give a reasonable window for most developers to change their code.</p>

<p>If you're an app developer, it's important to change your signing code as more containers begin to support OpenSocial 0.9. It's a simple change - just check for the <code>xoauth_public_key</code> parameter, and if it's not available, then look for <code>xoauth_signature_publickey</code> instead. Once 0.9 has been fully deployed, you should be able to delete the fallback (although keeping it around for a while shouldn't break anything).</p>]]></description>
            <link>http://roomanna.com/2009/08/changes-to-the-validating-sign.html</link>
            <guid>http://roomanna.com/2009/08/changes-to-the-validating-sign.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">compatibility</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">opensocial-0.9</category>
            
            
            <pubDate>Tue, 04 Aug 2009 11:38:22 -0800</pubDate>
        </item>
        
        <item>
            <title>Announcing the Developer Extension for OpenSocial</title>
            <description><![CDATA[<p> I really enjoy using <a href="http://getfirebug.com" target="_blank">Firebug</a> to debug my web applications. Nothing like being able to inspect items on the page, log debug information to the console, and execute arbitrary Javascript on the page to test out a quick fix.</p>

<p>When working with OpenSocial gadgets, I usually find myself using Firebug to inspect an IFrame to get the URL of the gadget spec that is being loaded. While Firebug gives me access to this data, it's a little hard to get to, and I need to decode the URL before I can paste it into a browser. So to help with this, I created a Firebug extension which scans the current page to see if any OpenSocial gadgets have been loaded. If the extension finds any gadgets, it attempts to discover the XML spec URLs for all the gadgets on the page and lists these as links which will go directly to the gadget XML spec. (Note that this feature works for Shindig based websites, but will not work on MySpace).</p>

<p>Additionally, I wanted to be able to execute JavaScript code inside of the gadget IFrame (and not the container page, which Firebug lets you do normally). This kind of functionality really help debug gadgets, because you can test out JavaScript without needing to save and upload an XML file again (or even reload the page!). So I added a box below each XML spec URL which will let you execute any JavaScript you want, in the context of the gadget's IFrame.</p>

<p>You can <a href="https://addons.mozilla.org/en-US/firefox/addon/13124/" target="_blank">find the extension on addons.mozilla.org here</a>. Please leave a review on that site if you wind up using it!</p>

<p style="text-align: center;"><img src="http://api.ning.com/files/Z2KSSjaNQNf9HgGi1x8jWaGgllnxeTdyr7oIRY288TMEXk46ImQcwQNdBesM3ivT7tm3LQVdWqs-N-CHqyhVOqTOOHRShuJN/1247859680.png" alt=""/></p>]]></description>
            <link>http://roomanna.com/2009/07/announcing-the-developer-exten.html</link>
            <guid>http://roomanna.com/2009/07/announcing-the-developer-exten.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">tools</category>
            
            
            <pubDate>Fri, 17 Jul 2009 14:36:26 -0800</pubDate>
        </item>
        
        <item>
            <title>OAuth got you down? Maybe this can help!</title>
            <description><![CDATA[<p> <img style="float: right; margin: 0 0 10px 10px;" src="http://wiki.opensocial.org/images/7/7a/Oauth_signed.png"/> OpenSocial has been tied to the <a href="http://oauth.net" target="_blank">OAuth</a> specification almost from the start, but it can be pretty confusing to try and figure out the differences between <b>two-legged OAuth</b>, <b>three-legged OAuth</b>, and <b>OAuth request signing</b> -- terms which are all thrown around pretty casually in the OpenSocial documentation.</p>

<p>To help make sense of it all, I've <a href="http://wiki.opensocial.org/index.php?title=OAuth_Use_Cases" target="_blank">updated the OAuth Use Cases page</a> on the OpenSocial wiki. You'll find additional diagrams and clearer request flows showing how data can be transferred between social networks, users, and third party application servers. Additionally, there are hypothetical examples showing where each type of OAuth comes in handy, as well as some links to container-specific resources for obtaining OAuth keys for your applications.</p>]]></description>
            <link>http://roomanna.com/2009/07/oauth-got-you-down-maybe-this.html</link>
            <guid>http://roomanna.com/2009/07/oauth-got-you-down-maybe-this.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">documentation</category>
            
            
            <pubDate>Thu, 16 Jul 2009 10:34:39 -0800</pubDate>
        </item>
        
        <item>
            <title>Upcoming changes to the User Agent string of Google-hosted containers</title>
            <description><![CDATA[<p>For those of you developing on a Google-run OpenSocial container (orkut, iGoogle, Google Friend Connect, or Gmail), please be aware that Google will be changing their User-Agent string for outgoing OpenSocial requests soon.</p>

<p>Previously, this string was:<br/>
<b>Google OpenSocial agent (http://www.google.com/feedfetcher.html)</b></p>

<p>When the change goes live, the string will be:<br />
<b>Mozilla/5.0 (compatible) Feedfetcher-Google; (+http://www.google.com/feedfetcher.html)</b></p>

<p>This will be the agent used for all outgoing requests, including fetching gadget specs, <a href="http://wiki.opensocial.org/index.php?title=Osapi.http_(v0.9)">osapi.http</a> or <a href="http://wiki.opensocial.org/index.php?title=Gadgets.io_(v0.8)#gadgets.io.makeRequest">gadgets.io.makeRequest</a> calls, and proxied content fetches.</p>

<p>We're expecting few developers to be affected by this change, so if you're not checking the User-Agent for requests to your server, you shouldn't have to make any changes.</p>]]></description>
            <link>http://roomanna.com/2009/06/upcoming-changes-to-the-user-a.html</link>
            <guid>http://roomanna.com/2009/06/upcoming-changes-to-the-user-a.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">compatibility</category>
            
            
            <pubDate>Thu, 18 Jun 2009 15:31:38 -0800</pubDate>
        </item>
        
        <item>
            <title>The OpenSocial PHP Client Library now has a &quot;Getting Started&quot; guide</title>
            <description><![CDATA[<p><img src="http://api.ning.com/files/nSdQ22R0G72z6uBmX3eqwBXSuB1BqImgHX-6Qb4YbcfkLgVjVeEV3ko*2PpWhJ7xxFwTk49si0gByaGVnP0sqR6zUfOO8hAt/logo.png" alt="" width="66" height="55" style="float: left; padding-right: 10px;"/> I'm happy to announce that we've just finished work on a preliminary <a href="http://code.google.com/p/opensocial-php-client/wiki/GettingStarted?tm=6">"Getting Started" guide</a> for the OpenSocial PHP client library.</p>

<p>This guide should help answer a lot of the questions people first have when starting to develop OpenSocial applications with PHP. We've covered such topics as getting and installing the library, how to batch requests and deal with errors, and how to make simple OpenSocial requests for People, Activities, and App Data. Also included is our <a href="http://code.google.com/p/opensocial-php-client/wiki/ProjectRoadmap">current roadmap</a> so you can see what we're working on.</p>

<p>While every effort has been made to create a comprehensive developer's guide, we certainly understand that there still may be areas of the client library which are not fully documented or where the examples are unclear. If you see any place where the documentation can be improved, please take a minute to file a feature request in our <a href="http://code.google.com/p/opensocial-php-client/issues/list">issue tracker</a>, and we'll be able to make the documentation better for everyone.</p>

<p>Happy Coding!<br />
~Arne (on behalf of the PHP client library team)</p>]]></description>
            <link>http://roomanna.com/2009/06/the-opensocial-php-client-libr.html</link>
            <guid>http://roomanna.com/2009/06/the-opensocial-php-client-libr.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">tools</category>
            
            
            <pubDate>Tue, 02 Jun 2009 15:28:14 -0800</pubDate>
        </item>
        
        <item>
            <title>OpenSocial&apos;s first birthday party</title>
            <description><![CDATA[If anyone is heading to the <a href="http://opensocialapis.blogspot.com/2008/11/opensocials-first-birthday-detailed.html">OpenSocial Birthday party at MySpace</a> next week, I'll be there to give a presentation on the <a href="http://osda.appspot.com/">OpenSocial Dev App</a> and to talk to developers about getting their apps running on multiple containers.&nbsp; See you there! ]]></description>
            <link>http://roomanna.com/2008/11/opensocials-first-birthday-par.html</link>
            <guid>http://roomanna.com/2008/11/opensocials-first-birthday-par.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">events</category>
            
            
            <pubDate>Fri, 07 Nov 2008 09:11:42 -0800</pubDate>
        </item>
        
        <item>
            <title>Presentation from DevFest Beijing</title>
            <description><![CDATA[In October, I was fortunate enough to be able to travel to Shanghai and Beijing for <a href="http://code.google.com/events/apacdevfest/">Google's DevFest developer events</a> in those cities.&nbsp; <br /><br />Presenting OpenSocial to developers who hadn't had as much exposure to the technology was a refreshing challenge.&nbsp; It made me look at our existing slide decks a bit more critically (especially since the slides were going to be translated) and I wound up creating a lot of content to explain the basic OpenSocial concepts.&nbsp; <br /><br />If you're a developer interested in OpenSocial but can't seem to find an overview of the entire technology stack (as of October 2008, at least), check out these slides - hopefully they'll give you some insight:<br /><br />

<div style="text-align: center;" id="__ss_686874"><a style="margin: 12px 0pt 3px; font-family: Helvetica,Arial,Sans-serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 14px; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none; display: block; text-decoration: underline;" href="http://www.slideshare.net/kurrik/open-social-tech-talk-beijing-presentation?type=powerpoint" title="Open Social Tech Talk   Beijing">Open Social Tech Talk   Beijing</a><object style="margin: 0px;" width="425" height="355"><param name="movie" value="http://static.slideshare.net/swf/ssplayer2.swf?doc=opensocial-tech-talk-beijing-1224823071621431-8&amp;stripped_title=open-social-tech-talk-beijing-presentation" /><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><embed src="http://static.slideshare.net/swf/ssplayer2.swf?doc=opensocial-tech-talk-beijing-1224823071621431-8&amp;stripped_title=open-social-tech-talk-beijing-presentation" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="355"></object><div style="font-size: 11px; font-family: tahoma,arial; height: 26px; padding-top: 2px;">View SlideShare <a style="text-decoration: underline;" href="http://www.slideshare.net/kurrik/open-social-tech-talk-beijing-presentation?type=powerpoint" title="View Open Social Tech Talk   Beijing on SlideShare">presentation</a> or <a style="text-decoration: underline;" href="http://www.slideshare.net/upload?type=powerpoint">Upload</a> your own. (tags: <a style="text-decoration: underline;" href="http://slideshare.net/tag/sns">sns</a> <a style="text-decoration: underline;" href="http://slideshare.net/tag/2008">2008</a>)</div></div>

<p><a href="http://www.slideshare.net/kurrik/opensocial-tech-talk-beijing-chinese-presentation/"><br /></a></p><p><a href="http://www.slideshare.net/kurrik/opensocial-tech-talk-beijing-chinese-presentation/">Here they are translated into Chinese</a>.&nbsp; My goal is to get some of the new images and diagrams into the official documentation soon.<br /></p>]]></description>
            <link>http://roomanna.com/2008/11/presentation-from-devfest-beij.html</link>
            <guid>http://roomanna.com/2008/11/presentation-from-devfest-beij.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">presentations</category>
            
            
            <pubDate>Thu, 06 Nov 2008 11:53:36 -0800</pubDate>
        </item>
        
        <item>
            <title>Sending private messages on Friendster</title>
            <description><![CDATA[I had to write a quick sample today to send a private message to the OWNER on Friendster.&nbsp; The following sends a message to your Friendster <a href="http://www.friendster.com/messages.php?folder=Inbox">message inbox</a>:<br /><br /><pre class="code">function sendNotification() {
  var params = {};
  params[opensocial.Message.Field.TITLE] =
      "Title of the notification goes here";
  params[opensocial.Message.Field.TYPE] =
      opensocial.Message.Type.PRIVATE_MESSAGE;
  var body="Text of the notification goes here";
  var message = opensocial.newMessage(body, params);
  var recipient = opensocial.DataRequest.PersonId.OWNER;
  opensocial.requestSendMessage(recipient, message,
      onSendNotification);
};

function onSendNotification(resp) {
  if (!resp.hadError() &amp;&amp; resp.getData().status == "sent") {
    alert("The message was sent to the OWNER");
  } else {
    alert("There was a problem: " + resp.getErrorMessage());
  }
};

sendNotification();<br /></pre>

Note the message type is set to <code>PRIVATE_MESSAGE</code>.&nbsp; Friendster also supports type <code>NOTIFICATION</code>, but I haven't quite figured out where that shows up, and I get a "Insufficient permissions for action 'publicMessage'" error message when trying <code>PUBLIC_MESSAGE</code>.<br /><br />Also note that this is for OpenSocial 0.7.&nbsp; If you're migrating this code to another container on 0.8, you'll need to change the IdSpec stuff (<a href="http://roomanna.com/2008/08/updating-your-apps-to-use-the.html">as I've covered before</a>).<br />]]></description>
            <link>http://roomanna.com/2008/09/sending-private-messages-on-fr.html</link>
            <guid>http://roomanna.com/2008/09/sending-private-messages-on-fr.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">opensocial-0.7</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">samples</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">friendster</category>
            
            <pubDate>Wed, 24 Sep 2008 11:09:58 -0800</pubDate>
        </item>
        
        <item>
            <title>Fetch by ID sample</title>
            <description><![CDATA[I needed to write the following sample of code to test fetching people by ID number.&nbsp; This is an interesting sample because it demonstrates handling an error condition - namely, the "unauthorized" response that you should get when you try to access an account that you don't have permission to request.&nbsp; On orkut, this means people who don't have your app installed, even if they're your friends.<br /><br />The following runs in <a href="http://roomanna.com/2008/08/introducing-dafos-quick-openso.html">DAfOS</a>:<br /><br /> <pre class="code">function onPersonGot(result) {
  var response = result.get("person");
  if (response.hadError()) {
    output("There was a problem fetching this user: " + 
        response.getErrorCode());
  } else {
    output("Fetched " + 
        result.get("person").getData().getDisplayName());
  }
  gadgets.window.adjustHeight();
};

function closeGetPerson(id) {
  return function() {
    var params = {};
    var req = opensocial.newDataRequest();
    req.add(req.newFetchPersonRequest(id, params), "person");
    req.send(onPersonGot);
  };
};


function closePrintFriend(list) {
  return function(friend) {
    var item = document.createElement("li");
    var link = document.createElement("a");
    var text = document.createTextNode(friend.getDisplayName());
    list.appendChild(item);
    item.appendChild(link);
    item.appendChild(document.createTextNode(" [" + 
        friend.getId() + "]"));
    link.appendChild(text);
    link.onclick = closeGetPerson(friend.getId());
    link.href = "javascript:void(0);";
  };
};

function gotFriends(data) {
  var friends = data.get("of").getData();
  var list = document.createElement("ul");
  var main = document.getElementById("dom_handle")
  main.innerHTML = "";
  main.appendChild(list);
  friends.each(closePrintFriend(list));
  gadgets.window.adjustHeight();
};

function getFriends() {
  var params = {};
  params[opensocial.DataRequest.PeopleRequestFields.MAX] = 1000;
  var req = opensocial.newDataRequest();
  req.add(req.newFetchPeopleRequest(
      opensocial.DataRequest.Group.OWNER_FRIENDS, params), "of");
  req.send(gotFriends);
};

getFriends();</pre>Note that the example lists the friends of the owner as links.&nbsp; Clicking on each name will attempt to retrieve that user by ID number.&nbsp; <br /><br /><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><img alt="fetch_by_ids_2.png" src="http://roomanna.com/2008/09/03/Picture%202.png" class="mt-image-none" style="" width="342" height="17" /></span><br /><br />On orkut, if a user doesn't have DAfOS installed, you'll get an "unauthorized" error:<br /><br /><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><img alt="fetch_by_ids_1.png" src="http://roomanna.com/2008/09/03/Picture%201.png" class="mt-image-none" style="" width="500" height="65" /></span><br />
<div><br />In your applications, make sure to handle cases like this, since you won't always be able to guarantee that all containers will have the same policies around which user accounts you may directly access.<br /></div><div><br /></div>]]></description>
            <link>http://roomanna.com/2008/09/fetch-by-id-sample.html</link>
            <guid>http://roomanna.com/2008/09/fetch-by-id-sample.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">opensocial-0.7</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">samples</category>
            
            
            <pubDate>Wed, 03 Sep 2008 00:42:07 -0800</pubDate>
        </item>
        
        <item>
            <title>Updating your apps to use the IdSpec object in OpenSocial 0.8</title>
            <description><![CDATA[Lately I've been updating some documentation to use version of 0.8 of the OpenSocial specification.&nbsp; If you've developed on the 0.7 version of the API, you'll probably be happy to see that not a lot of breaking changes have been introduced in the new version, with one major exception: the <code>IdSpec</code> object.<br /><br />In the past, when you wanted to specify a single person or a group of people, you would use one of the following:<br /><br />Single person specifiers (OpenSocial 0.7):<br /><ul><li><code>opensocial.DataRequest.Person.OWNER</code></li><li><code>opensocial.DataRequest.Person.VIEWER</code></li><li>A string representing the OpenSocial ID of a person.</li></ul>Multiple person specifiers (OpenSocial 0.7):<br /><ul><li><code>opensocial.DataRequest.Group.OWNER_FRIENDS</code></li><li><code>opensocial.DataRequest.Group.VIEWER_FRIENDS</code></li><li>An array of strings, each representing the OpenSocial ID of a person.</li></ul>In 0.8, the idea of an <code>IdSpec</code> object was introduced.&nbsp; <code>IdSpec</code> allows you to be much more expressive when specifying groups of people (including friends-of-friends, covered later) but introduces some additional complexity.&nbsp; Single person specifiers still use the <code>OWNER</code> and <code>VIEWER</code> objects, but these have been moved to the <code>opensocial.IdSpec.PersonId</code> namespace.<br /><br />To convert your app, update all functions that take a single person identifier to one of the following:<br /><ul><li><code>opensocial.IdSpec.PersonId.OWNER</code></li><li><code>opensocial.IdSpec.PersonId.VIEWER</code></li><li>A string representing the OpenSocial ID of a person.</li></ul>Note that only the following take a single person modifier: <br /><ul><li><code>opensocial.DataRequest.newFetchPersonRequest</code></li><li><code>opensocial.DataRequest.newUpdatePersonAppDataRequest</code></li><li><code>opensocial.DataRequest.newRemovePersonAppDataRequest</code>&nbsp; <br /></li></ul>The last two only accept the value of <code>opensocial.IdSpec.PersonId.VIEWER</code>, so this is a pretty straightforward change.<br /><br />Seleting a group of people requires a bit more of a code change, though.&nbsp; Where you might write something like this in OpenSocial 0.7:<br /><br />
<pre class="code">var params = {};
var req = opensocial.newDataRequest();
...
req.add(req.newFetchPeopleRequest(
    opensocial.DataRequest.Group.OWNER_FRIENDS, params);
req.send();
</pre>
Now you need to create an <code>IdSpec</code> instead:<br /><br />
<pre class="code">var params = {};
var idspec = opensocial.newIdSpec({ 
    "userId" : "OWNER", 
    "groupId" : "FRIENDS" 
});
...<br />req.add(req.newFetchPeopleRequest(
    idspec, params);
req.send();
</pre> 
You can actually create <code>IdSpec</code> equivalents to all of the old person/people identifiers:<br /><br />
<table class="tabular"><tbody>
  <tr><th>Identifier</th><th><code>IdSpec</code> code</th></tr>
  <tr><td><strong>OWNER</strong></td><td><pre class="code">var idspec = opensocial.newIdSpec({ 
    "userId" : "OWNER",  "groupId" : "SELF" 
});</pre></td></tr>
  <tr class="alt"><td><strong>VIEWER</strong></td><td><pre class="code">var idspec = opensocial.newIdSpec({ 
    "userId" : "VIEWER",  "groupId" : "SELF" 
});</pre></td></tr>
  <tr><td><strong>OWNER_FRIENDS</strong></td><td><pre class="code">var idspec = opensocial.newIdSpec({ 
    "userId" : "OWNER",  "groupId" : "FRIENDS" 
});</pre></td></tr>
  <tr class="alt"><td><strong>VIEWER_FRIENDS</strong></td><td><pre class="code">var idspec = opensocial.newIdSpec({ 
    "userId" : "VIEWER",  "groupId" : "FRIENDS" 
});</pre></td></tr>
</tbody></table>
<br />You can use these for the following functions:<br /><ul><li><code>opensocial.DataRequest.newFetchActivitiesRequest</code></li><li><code>opensocial.DataRequest.newFetchPeopleRequest</code></li><li><code>opensocial.DataRequest.newFetchPersonAppDataRequest</code></li></ul><br />The <code>IdSpec</code> object exposes some additional functionality like <code>NETWORK_DISTANCE</code> that I'll cover later, but for the time being, this should be enough information to get you to start porting your existing code to 0.8. <br /><br /><br />]]></description>
            <link>http://roomanna.com/2008/08/updating-your-apps-to-use-the.html</link>
            <guid>http://roomanna.com/2008/08/updating-your-apps-to-use-the.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">opensocial-0.8</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">samples</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">idspec</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">opensocial-0.8</category>
            
            <pubDate>Fri, 22 Aug 2008 17:43:15 -0800</pubDate>
        </item>
        
        <item>
            <title>Introducing DAfOS: Quick OpenSocial testing</title>
            <description><![CDATA[When teaching myself the OpenSocial API, I found the standard "edit XML file" -&gt; "upload to server" -&gt; "reload gadget" process to be too slow for my liking, especially when working with code that was almost completely client-side JavaScript.&nbsp; <br /><br />A strength (or weakness, depending on who you ask) of JavaScript is that you can compile and execute JavaScript source code at runtime using the <code>eval</code> function.&nbsp; It made sense to create a simple gadget to help developers prototype simple OpenSocial calls, so I released CodeRunner, an OpenSocial application that let developers execute JavaScript snippets inside of a live OpenSocial container.&nbsp; These snippets could also be saved to AppData, which was convenient as long as you didn't run out of quota space (currently 10k on orkut and 1k on MySpace).<br /><br />CodeRunner wound up working quite well, but I wanted more space for storage, and I wanted to offer some capabilities that only a server-side solution would be able to satisfy.&nbsp; Because Google released their App Engine product around this time, I decided to turn CodeRunner into an App Engine application, called the Developer Application for OpenSocial, or DAfOS for short.<br /><br />You can get links to use DAfOS on different containers by visiting <a href="http://dafos.appspot.com/">dafos.appspot.com</a>.&nbsp; Eventually that site will be filled out with more documentation.&nbsp; <br />&nbsp;<br />Here's a shot of DAfOS in action (it looks a lot like CodeRunner at the moment):<br /><br /><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><img alt="DAfOS.png" src="http://roomanna.com/2008/08/20/Picture%202.png" class="mt-image-none" style="" height="250" width="600" /></span><br /><div><br /><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><img alt="DAfOS_execute.png" src="http://roomanna.com/2008/08/20/Picture%204.png" class="mt-image-right" style="margin: 0pt 0pt 20px 20px; float: right;" height="38" width="98" /></span>Samples are entered into the yellow input box.&nbsp; You can run a sample by clicking the "Execute" button in the top right hand corner of the gadget.&nbsp; The JavaScript entered in the box will execute as if it were part of the gadget itself.&nbsp; That means that you can execute social data queries, post Activity Stream entries, send messages, and anything else that the OpenSocial API allows.<br /><br />DAfOS also defines a method called <code>output</code>.&nbsp; Everything you pass to this method will be printed out in an output box at the bottom of the application.&nbsp; If you have <a href="http://getfirebug.com/">Firebug</a> installed (you really should!), then you'll see this output in Firebug's console, as well.<br /><br /><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><img alt="Picture 7.png" src="http://roomanna.com/2008/08/20/Picture%207.png" class="mt-image-none" style="" height="127" width="600" /></span><br /><br />Since DAfOS runs on App Engine, the samples are no longer stored in AppData.&nbsp; When you save a sample, it is actually hosted at dafos.appspot.com, and accessible by clicking on the name of the sample after you save it.&nbsp; This URL can be sent out to help supply code for reporting issues or helping other developers with problems.<br /><br /><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><img alt="DAfOS_controls.png" src="http://roomanna.com/2008/08/20/Picture%206.png" class="mt-image-none" style="" height="72" width="600" /></span><br /><br />Because I use DAfOS to write most of my samples, you'll be able to copy and paste most of the code snippets from this blog directly into DAfOS and watch them run.<br /><br />You can still use CodeRunner by installing <a href="http://opensocial-resources.googlecode.com/svn/samples/coderunner/trunk/coderunner.xml">this gadget XML spec</a> to a container, but there will not be any future development on it, meaning it will likely stop functioning once containers switch to OpenSocial 0.8<br /></div><div><br /></div>]]></description>
            <link>http://roomanna.com/2008/08/introducing-dafos-quick-openso.html</link>
            <guid>http://roomanna.com/2008/08/introducing-dafos-quick-openso.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">tools</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">dafos testing javascript tools</category>
            
            <pubDate>Wed, 20 Aug 2008 12:38:14 -0800</pubDate>
        </item>
        
    </channel>
</rss>
