<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blog &#187; omgoogle</title>
	<atom:link href="http://antimatter15.com/wp/tag/omgoogle/feed/" rel="self" type="application/rss+xml" />
	<link>http://antimatter15.com/wp</link>
	<description>this title probably isn&#039;t very original</description>
	<lastBuildDate>Fri, 23 Jul 2010 21:21:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Wave uses Closure</title>
		<link>http://antimatter15.com/wp/2009/11/wave-uses-closure/</link>
		<comments>http://antimatter15.com/wp/2009/11/wave-uses-closure/#comments</comments>
		<pubDate>Sun, 08 Nov 2009 22:27:38 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Wave]]></category>
		<category><![CDATA[closure]]></category>
		<category><![CDATA[magic]]></category>
		<category><![CDATA[omgoogle]]></category>
		<category><![CDATA[wave]]></category>

		<guid isPermaLink="false">http://antimatter15.com/wp/?p=888</guid>
		<description><![CDATA[Closure Tools were recently released by Google to allow for others to use the same rich libraries that Google uses internally. Its used by Gmail, Google Docs and Google Maps, but interestingly also used by Google Wave. While they don&#8217;t actually announce that Closure is used in Wave, the view-source obfuscated mess from Wave does [...]]]></description>
			<content:encoded><![CDATA[<p>Closure Tools were <a href="http://googlecode.blogspot.com/2009/11/introducing-closure-tools.html">recently released</a> by Google to allow for others to use the same rich libraries that Google uses internally. Its used by Gmail, Google Docs and Google Maps, but interestingly also used by Google Wave. While they don&#8217;t actually announce that Closure is used in Wave, the view-source obfuscated mess from Wave does strongly show it.The reason why its use in wave is more interesting than most others is that Wave is in GWT, while the rest are pure JS. This implies that an interface to the Closure Library may be coming to GWT. While the interface doesn&#8217;t seem to be made from Closure, there are references to &#8220;closure_hashCode&#8221; and &#8220;goog.net.BrowserChannel&#8221;.</p>
]]></content:encoded>
			<wfw:commentRss>http://antimatter15.com/wp/2009/11/wave-uses-closure/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>with:public not working</title>
		<link>http://antimatter15.com/wp/2009/10/withpublic-not-working/</link>
		<comments>http://antimatter15.com/wp/2009/10/withpublic-not-working/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 03:55:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Wave]]></category>
		<category><![CDATA[googlewave]]></category>
		<category><![CDATA[omgoogle]]></category>
		<category><![CDATA[troubleshooting]]></category>

		<guid isPermaLink="false">http://antimatter15.com/wp/2009/10/withpublic-not-working/</guid>
		<description><![CDATA[It seems that after a recent update to wave, with:public only shows the waves which are already in your inbox. A simple remedy is to use group:public@a.gwave.com instead of with:public. I found it on http://www.google.com/support/forum/p/wave/thread?tid=10eaba86d62c005c&#038;hl=en]]></description>
			<content:encoded><![CDATA[<p>It seems that after a recent update to wave, with:public only shows the waves which are already in your inbox. A simple remedy is to use group:public@a.gwave.com instead of with:public. I found it on http://www.google.com/support/forum/p/wave/thread?tid=10eaba86d62c005c&#038;hl=en </p>
]]></content:encoded>
			<wfw:commentRss>http://antimatter15.com/wp/2009/10/withpublic-not-working/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Scroll Bar Improvements</title>
		<link>http://antimatter15.com/wp/2009/09/scroll-bar-improvements/</link>
		<comments>http://antimatter15.com/wp/2009/09/scroll-bar-improvements/#comments</comments>
		<pubDate>Sat, 19 Sep 2009 02:40:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[omgoogle]]></category>

		<guid isPermaLink="false">http://antimatter15.com/wp/?p=845</guid>
		<description><![CDATA[So I was reading through some long-ish articles, and logically, I stare at the scrollbar to get a rough estimation of where I am in reading it. But, the horrible thing called comments and a *gasp* theme, makes the page appear FAR longer than the article. I think that browsers, with the new &#60;section&#62; &#60;header&#62; [...]]]></description>
			<content:encoded><![CDATA[<p>So I was reading through some long-ish articles, and logically, I stare at the scrollbar to get a rough estimation of where I am in reading it.</p>
<p>But, the horrible thing called comments and a *gasp* theme, makes the page appear FAR longer than the article. I think that browsers, with the new &lt;section&gt; &lt;header&gt; and whatever that&#8217;s in HTML5 should interpret these markings and create a smarter scrollbar like how Chrome does the statusbar with little yellow markings where occurances are found. There should be ones which indicate the end of the article, start of comments, etc.</p>
<p>And I&#8217;ve noticing how I&#8217;m talking about Google for just about every new post. I think that&#8217;s just abou where all the innovation is right now. Or at least all the innovation that I use and know about that gets popularized by media.</p>
]]></content:encoded>
			<wfw:commentRss>http://antimatter15.com/wp/2009/09/scroll-bar-improvements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->