<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.0.4" -->
<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/"
	>

<channel>
	<title>Clientside</title>
	<link>http://clientside.cnet.com</link>
	<description>Making stuff work on the other side of the request.</description>
	<pubDate>Tue, 06 May 2008 01:03:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>
	<language>en</language>
			<item>
		<title>Autocompleter and Slimbox converted for MooTools 1.2</title>
		<link>http://clientside.cnet.com/cnet-js-standards/autocompleter-and-slimbox-converted-for-mootools-12/</link>
		<comments>http://clientside.cnet.com/cnet-js-standards/autocompleter-and-slimbox-converted-for-mootools-12/#comments</comments>
		<pubDate>Tue, 06 May 2008 01:03:44 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
		
	<category>CNET JS Standards</category>
		<guid isPermaLink="false">http://clientside.cnet.com/cnet-js-standards/autocompleter-and-slimbox-converted-for-mootools-12/</guid>
		<description><![CDATA[In our last post we went through all the new goodies that can be found in our release candidate of our code for MooTools 1.2. We&#8217;ve spent a bit of time fixing the few bugs we&#8217;ve found and gotten emails about (thanks!) and also converted our copies of Autocompleter (authored by Harald Krishner) and also [...]]]></description>
		<wfw:commentRSS>http://clientside.cnet.com/cnet-js-standards/autocompleter-and-slimbox-converted-for-mootools-12/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Clientside Libraries 1.2 RC2</title>
		<link>http://clientside.cnet.com/cnet-js-standards/clientside-libraries-12-rc2/</link>
		<comments>http://clientside.cnet.com/cnet-js-standards/clientside-libraries-12-rc2/#comments</comments>
		<pubDate>Mon, 28 Apr 2008 19:04:52 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
		
	<category>CNET JS Standards</category>
	<category>MooTools</category>
		<guid isPermaLink="false">http://clientside.cnet.com/cnet-js-standards/clientside-libraries-12-rc2/</guid>
		<description><![CDATA[After a lot of start and stop work I&#8217;m happy to announce that CNET&#8217;s javascript libraries are now nearing final release for MooTools 1.2 compatibility. We announced our RC1 release of the libraries. We&#8217;ve spent the time since then writing lots and lots of tests to validate the codebase. At this point we&#8217;ve spent all [...]]]></description>
		<wfw:commentRSS>http://clientside.cnet.com/cnet-js-standards/clientside-libraries-12-rc2/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>CiUI Dev on Google Code</title>
		<link>http://clientside.cnet.com/best-practices/ciui-dev-on-google-code/</link>
		<comments>http://clientside.cnet.com/best-practices/ciui-dev-on-google-code/#comments</comments>
		<pubDate>Fri, 04 Apr 2008 17:59:13 +0000</pubDate>
		<dc:creator>Vladimir Olexa</dc:creator>
		
	<category>Best practices</category>
	<category>Organizing code</category>
	<category>AJAX</category>
	<category>CNET JS Standards</category>
	<category>Widgets</category>
		<guid isPermaLink="false">http://clientside.cnet.com/uncategorized/ciui-dev-on-google-code/</guid>
		<description><![CDATA[I&#8217;ve created a new development repository on Google Code. I wanted to have a separate development environment for people to work on the library without having to work off of the entire CNET Javascript framework repository. I&#8217;ll be posting CiUI-only releases there before merging them with Clientside&#8217;s repository.
You can also file CiUI specific bugs and [...]]]></description>
		<wfw:commentRSS>http://clientside.cnet.com/best-practices/ciui-dev-on-google-code/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>$merge, $extend, Class.extend, Class.implement, Native.implement</title>
		<link>http://clientside.cnet.com/best-practices/merge-extend-classextend-classimplement-nativeimplement/</link>
		<comments>http://clientside.cnet.com/best-practices/merge-extend-classextend-classimplement-nativeimplement/#comments</comments>
		<pubDate>Fri, 28 Mar 2008 21:06:49 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
		
	<category>Best practices</category>
	<category>Examples</category>
	<category>Reference</category>
	<category>MooTools</category>
		<guid isPermaLink="false">http://clientside.cnet.com/best-practices/merge-extend-classextend-classimplement-nativeimplement/</guid>
		<description><![CDATA[So I was asked yesterday the following:
Why does Browser use merge but Element use implement?
And after composing a lengthy reply, I thought it might be useful to post it for others:
Browser is a Hash, which doesn’t have an implement method. The .merge method here is referring to its own method which is similar to $merge, [...]]]></description>
		<wfw:commentRSS>http://clientside.cnet.com/best-practices/merge-extend-classextend-classimplement-nativeimplement/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>CiUI - CNET iPhone UI</title>
		<link>http://clientside.cnet.com/cnet-js-standards/ciui-cnet-iphone-ui/</link>
		<comments>http://clientside.cnet.com/cnet-js-standards/ciui-cnet-iphone-ui/#comments</comments>
		<pubDate>Tue, 18 Mar 2008 23:40:22 +0000</pubDate>
		<dc:creator>Vladimir Olexa</dc:creator>
		
	<category>CNET JS Standards</category>
	<category>Widgets</category>
		<guid isPermaLink="false">http://clientside.cnet.com/cnet-js-standards/ciui-cnet-iphone-ui/</guid>
		<description><![CDATA[Given how the iPhone's growth has made some ripples in the world of mobile browsing, we here at CNET decided to spend a little time and make an iPhone friendly version of our sites. At first I (Vladimir Olexa) considered the excellent iUI from Joe Hewitt but eventually decided to write our own.
The result is [...]]]></description>
		<wfw:commentRSS>http://clientside.cnet.com/cnet-js-standards/ciui-cnet-iphone-ui/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Clientside for Mootools 1.2 - RC1 (a long time coming)</title>
		<link>http://clientside.cnet.com/cnet-js-standards/clientside-for-mootools-12-rc1-a-long-time-coming/</link>
		<comments>http://clientside.cnet.com/cnet-js-standards/clientside-for-mootools-12-rc1-a-long-time-coming/#comments</comments>
		<pubDate>Tue, 11 Mar 2008 23:59:18 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
		
	<category>CNET JS Standards</category>
	<category>MooTools</category>
		<guid isPermaLink="false">http://clientside.cnet.com/cnet-js-standards/clientside-for-mootools-12-rc1-a-long-time-coming/</guid>
		<description><![CDATA[After many hours of toil we're ready to release our first candidate of our public libraries. We've put a lot of work into keeping up with Mootools 1.2 and all its goodness, so hopefully the wait has been worth it.
First up, changes!
We've refactored nearly the entire library and in most cases the changes don't affect [...]]]></description>
		<wfw:commentRSS>http://clientside.cnet.com/cnet-js-standards/clientside-for-mootools-12-rc1-a-long-time-coming/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Firecookie: Put your hand in the cookie jar with Firebug</title>
		<link>http://clientside.cnet.com/tools/browser-plugins/firecookie-put-your-hand-in-the-cookie-jar-with-firebug/</link>
		<comments>http://clientside.cnet.com/tools/browser-plugins/firecookie-put-your-hand-in-the-cookie-jar-with-firebug/#comments</comments>
		<pubDate>Thu, 06 Mar 2008 19:53:56 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
		
	<category>Browser Plugins</category>
		<guid isPermaLink="false">http://clientside.cnet.com/tools/browser-plugins/firecookie-put-your-hand-in-the-cookie-jar-with-firebug/</guid>
		<description><![CDATA[via Ajaxian:
Jan Odvárko "missed two movie nights" to create cookie support in Firebug. His Firebug plugin, Firecookie, gives you access to view, search, create, remove, and manage the permissions of a cookie, all from within a Firebug tab.
Firecookie creates a log entry every time when a cookie is created, changed, deleted or rejected (an option [...]]]></description>
		<wfw:commentRSS>http://clientside.cnet.com/tools/browser-plugins/firecookie-put-your-hand-in-the-cookie-jar-with-firebug/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Mootools 1.2 is close - but what about the CNET codebase?</title>
		<link>http://clientside.cnet.com/cnet-js-standards/mootools-12-is-close-but-what-about-the-cnet-codebase/</link>
		<comments>http://clientside.cnet.com/cnet-js-standards/mootools-12-is-close-but-what-about-the-cnet-codebase/#comments</comments>
		<pubDate>Mon, 25 Feb 2008 21:21:40 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
		
	<category>CNET JS Standards</category>
		<guid isPermaLink="false">http://clientside.cnet.com/cnet-js-standards/mootools-12-is-close-but-what-about-the-cnet-codebase/</guid>
		<description><![CDATA[Hi Gang,
I've been picking up more and more chatter regarding the imminent release of Mootools 1.2b and I keep getting emails and whatnot asking about CNET's codebase, which works in 1.11, but not so well in 1.2 (even with the Mootools compatibility layer).
We're working on it and we've made a lot of progress. We've now [...]]]></description>
		<wfw:commentRSS>http://clientside.cnet.com/cnet-js-standards/mootools-12-is-close-but-what-about-the-cnet-codebase/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Mobile Applications, RIP</title>
		<link>http://clientside.cnet.com/industry-news/mobile-applications-rip/</link>
		<comments>http://clientside.cnet.com/industry-news/mobile-applications-rip/#comments</comments>
		<pubDate>Mon, 25 Feb 2008 21:13:04 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
		
	<category>'Industry' news</category>
		<guid isPermaLink="false">http://clientside.cnet.com/industry-news/mobile-applications-rip/</guid>
		<description><![CDATA[Ajaxian has a post up about an article from the former VP of Palm regarding the death of Mobile Application development at the hands of the web. I've been chewing on a mobile web app in my head the last few weeks for my startup (I still spend time at CNET, I also recently launched [...]]]></description>
		<wfw:commentRSS>http://clientside.cnet.com/industry-news/mobile-applications-rip/feed/</wfw:commentRSS>
		</item>
		<item>
		<title>Error handling in javascript</title>
		<link>http://clientside.cnet.com/uncategorized/error-handling-in-javascript/</link>
		<comments>http://clientside.cnet.com/uncategorized/error-handling-in-javascript/#comments</comments>
		<pubDate>Thu, 24 Jan 2008 20:49:41 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
		
	<category>Uncategorized</category>
	<category>Server-side integration</category>
	<category>Optimization</category>
		<guid isPermaLink="false">http://clientside.cnet.com/uncategorized/error-handling-in-javascript/</guid>
		<description><![CDATA[I was helping someone today with their javascript and they asked me about how and when I manage errors in the classes and functions that I write. I wrote him back an email which I think actually could be useful to others, so here it is.
There are three types of error handling that I use:

Graceful: [...]]]></description>
		<wfw:commentRSS>http://clientside.cnet.com/uncategorized/error-handling-in-javascript/feed/</wfw:commentRSS>
		</item>
	</channel>
</rss>
