<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Google: gadgets &#038; mashups</title>
	<atom:link href="http://nonsmokingarea.com/blog/2006/10/04/google-gadgets-mashups/feed/" rel="self" type="application/rss+xml" />
	<link>http://nonsmokingarea.com/blog/2006/10/04/google-gadgets-mashups/</link>
	<description></description>
	<pubDate>Fri, 21 Nov 2008 20:49:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: nonsmokingarea.com &#187; Blog Archive &#187; widgets all over the place!</title>
		<link>http://nonsmokingarea.com/blog/2006/10/04/google-gadgets-mashups/#comment-2824</link>
		<dc:creator>nonsmokingarea.com &#187; Blog Archive &#187; widgets all over the place!</dc:creator>
		<pubDate>Tue, 07 Nov 2006 20:54:08 +0000</pubDate>
		<guid isPermaLink="false">http://nonsmokingarea.com/blog/?p=385#comment-2824</guid>
		<description>[...] while I tend to find most widget-engines quite generic and similar in featuresets, SpringWidgets is unique in several ways: while competing platforms run their widgets either on the local desktop (f.e. Yahoo! Widgets, ex Konfabulator) or exclusively on the web (f.e. Google Gadgets), SpringWidgets&#8217; code can be executed in both environments. widgets like the RSS-reader on the sidebar of this page, can be easily pulled to the desktop by just clicking the green cog (top-left). the desktop-software SpringBox is currently available for Windows only, with a Mac OS-version to follow soon. SpringWidgets integration with several social networking-sites is even better: widgets can be sent to profile pages on myspace, friendster, hi5 and xanga with a single click. as usual, html-snippets are used to get SpringWidgets on any other webpage (see screenshot below). [...]</description>
		<content:encoded><![CDATA[<p>[...] while I tend to find most widget-engines quite generic and similar in featuresets, SpringWidgets is unique in several ways: while competing platforms run their widgets either on the local desktop (f.e. Yahoo! Widgets, ex Konfabulator) or exclusively on the web (f.e. Google Gadgets), SpringWidgets&#8217; code can be executed in both environments. widgets like the RSS-reader on the sidebar of this page, can be easily pulled to the desktop by just clicking the green cog (top-left). the desktop-software SpringBox is currently available for Windows only, with a Mac OS-version to follow soon. SpringWidgets integration with several social networking-sites is even better: widgets can be sent to profile pages on myspace, friendster, hi5 and xanga with a single click. as usual, html-snippets are used to get SpringWidgets on any other webpage (see screenshot below). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nonsmokingarea.com &#187; Blog Archive &#187; dev: Google Code Search</title>
		<link>http://nonsmokingarea.com/blog/2006/10/04/google-gadgets-mashups/#comment-1818</link>
		<dc:creator>nonsmokingarea.com &#187; Blog Archive &#187; dev: Google Code Search</dc:creator>
		<pubDate>Thu, 05 Oct 2006 22:24:35 +0000</pubDate>
		<guid isPermaLink="false">http://nonsmokingarea.com/blog/?p=385#comment-1818</guid>
		<description>[...] looks like Google ain&#8217;t going to slow down these days: Code Search - Google&#8217;s effort on indexing source-code on the web - was launched earlier today. Code Search offers developers powerful ways (read: regular expressions) to search for code-snippets in any particular language, under any specific license. a quick test-drive unveiled that Code Search suffers from similar problems like established competitors Krugle and Koders: string-based search-results often mistake underlying semantics. when searching for an id3-implementation in PHP, results often lead to external function-calls, but not the actual source implementing id3. still, indexing source-code will definitely help making open source knowledge more accessible to average developers, not able/willing to spend hours/days to dissect code. looking forward on Danny Sullivan&#8217;s commentary on Code Search&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] looks like Google ain&#8217;t going to slow down these days: Code Search - Google&#8217;s effort on indexing source-code on the web - was launched earlier today. Code Search offers developers powerful ways (read: regular expressions) to search for code-snippets in any particular language, under any specific license. a quick test-drive unveiled that Code Search suffers from similar problems like established competitors Krugle and Koders: string-based search-results often mistake underlying semantics. when searching for an id3-implementation in PHP, results often lead to external function-calls, but not the actual source implementing id3. still, indexing source-code will definitely help making open source knowledge more accessible to average developers, not able/willing to spend hours/days to dissect code. looking forward on Danny Sullivan&#8217;s commentary on Code Search&#8230; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
