<?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>Clientcide (Formerly CNET's Clientside) &#187; moo.fx</title>
	<atom:link href="http://www.clientcide.com/category/3rd-party-libraries/moofx/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clientcide.com</link>
	<description>Making stuff work on the other side of the request.</description>
	<lastBuildDate>Fri, 06 Jan 2012 17:03:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>MooTools followup</title>
		<link>http://www.clientcide.com/3rd-party-libraries/mootools-followup/</link>
		<comments>http://www.clientcide.com/3rd-party-libraries/mootools-followup/#comments</comments>
		<pubDate>Wed, 20 Sep 2006 17:34:44 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[3rd Party Libraries]]></category>
		<category><![CDATA[CNET JS Standards]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Optimization]]></category>
		<category><![CDATA[Prototype]]></category>
		<category><![CDATA[Scriptactulous]]></category>
		<category><![CDATA[moo.fx]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=161</guid>
		<description><![CDATA[So I posted yesterday in my flurry of catch-up posts about the mad4milk.net guys new framework: MooTools. I&#8217;ve had a little time to dig into it and I must say that I&#8217;m blown away. In many ways, this is the framework that I&#8217;d say CNET should write for itself if it were to take on [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/3rd-party-libraries/mootools-followup/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Mootools</title>
		<link>http://www.clientcide.com/3rd-party-libraries/mootools/</link>
		<comments>http://www.clientcide.com/3rd-party-libraries/mootools/#comments</comments>
		<pubDate>Tue, 19 Sep 2006 18:55:22 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA['Industry' News]]></category>
		<category><![CDATA[3rd Party Libraries]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Code Snippets]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Manipulating the Dom]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[Visual Effects]]></category>
		<category><![CDATA[moo.fx]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=157</guid>
		<description><![CDATA[Well crap. 1) I love the mad4milk guys (makers of moo.fx, moo.ajax, moo.dom, prototype.lite). 2) their new framework looks AWESOME. 3) as always, their libraries are SUPER TINY.
But damn, now I have to learn something new, and maybe rewrite a bunch of crap. This is the problem with javascript. Still, when Prototype + Scriptaculous is [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/3rd-party-libraries/mootools/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Memory leaks and Moo.fx</title>
		<link>http://www.clientcide.com/best-practices/memory-leaks-and-moofx/</link>
		<comments>http://www.clientcide.com/best-practices/memory-leaks-and-moofx/#comments</comments>
		<pubDate>Mon, 26 Jun 2006 19:00:12 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Browser Bugs]]></category>
		<category><![CDATA[Optimization]]></category>
		<category><![CDATA[moo.fx]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=113</guid>
		<description><![CDATA[Continuing in my efforts to make my code stop leaking (fun!), I&#8217;ve been working on a popup handler I wrote recently (which I plan to post and share as soon as, you know, it doesn&#8217;t leak). 
This popup handler accepts as it&#8217;s parameters (among other things) a group of items (links for example) that it [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/memory-leaks-and-moofx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rewriting Prototype to get rid of that ugly side</title>
		<link>http://www.clientcide.com/3rd-party-libraries/prototype/rewriting-prototype-to-get-rid-of-that-ugly-side/</link>
		<comments>http://www.clientcide.com/3rd-party-libraries/prototype/rewriting-prototype-to-get-rid-of-that-ugly-side/#comments</comments>
		<pubDate>Tue, 30 May 2006 17:58:09 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[CNET JS Standards]]></category>
		<category><![CDATA[Prototype]]></category>
		<category><![CDATA[moo.fx]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=102</guid>
		<description><![CDATA[As part of a recent effort to make the CNET headers a little slimmer and to address some possible conflicts with our code and the javascript that runs from ad developers, I took some time last friday to rewrite Prototype.lite.js &#8211; distributed by the mad4milk guys (who make moo.fx). 
In my previous post I outlined [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/3rd-party-libraries/prototype/rewriting-prototype-to-get-rid-of-that-ugly-side/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>moo.dom &#8211; easily target html elements &amp; add actions</title>
		<link>http://www.clientcide.com/3rd-party-libraries/moodom-easily-target-html-elements-add-actions/</link>
		<comments>http://www.clientcide.com/3rd-party-libraries/moodom-easily-target-html-elements-add-actions/#comments</comments>
		<pubDate>Fri, 14 Apr 2006 20:34:01 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[3rd Party Libraries]]></category>
		<category><![CDATA[Visual Effects]]></category>
		<category><![CDATA[moo.fx]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=77</guid>
		<description><![CDATA[Those crazy guys at mad4milk.net have added a bit more to the moo.fx library. Now, in addition to their animation library, prototype-lite, and ajax-lite scripts, they&#8217;ve added a 3kb selector library: moo.dom

moo.dom is a very lightweight (less than 3kb!) and effective script, to target html elements using javascript and css selectors.
It uses prototype.js, or the [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/3rd-party-libraries/moodom-easily-target-html-elements-add-actions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lightbox + Moo.fx = slickness</title>
		<link>http://www.clientcide.com/code-snippets/visual-effects/lightbox-moofx-slickness/</link>
		<comments>http://www.clientcide.com/code-snippets/visual-effects/lightbox-moofx-slickness/#comments</comments>
		<pubDate>Tue, 21 Feb 2006 19:07:59 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Examples]]></category>
		<category><![CDATA[Visual Effects]]></category>
		<category><![CDATA[moo.fx]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=41</guid>
		<description><![CDATA[Check out this post on this crafty lightbox + moo.fx combination.
While Lightbox is really excellent, the sudden transition from page to image is a little bit jolting. I decided that integrating a Javascript effects library (in this case, my preferred option, the super-lightweight Moo.FX) into Lightbox would provide a more gentle transition from page to [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/visual-effects/lightbox-moofx-slickness/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Download.com Launches User Watch Lists</title>
		<link>http://www.clientcide.com/jsexamples/downloadcom-launches-user-watch-lists/</link>
		<comments>http://www.clientcide.com/jsexamples/downloadcom-launches-user-watch-lists/#comments</comments>
		<pubDate>Fri, 10 Feb 2006 21:52:19 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Examples]]></category>
		<category><![CDATA[moo.fx]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=19</guid>
		<description><![CDATA[Today Download.com rolled out our Watch List product. Users can add items to their list (ajax goodness) and, when said items are updated, they&#8217;ll get an email.
Additional features
Users have the option of having items that they download automatically added to their watch list; this helps them keep their software up to date.
Users can use a [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/jsexamples/downloadcom-launches-user-watch-lists/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Moo.fx version 1.2</title>
		<link>http://www.clientcide.com/3rd-party-libraries/moofx/moofx-version-12/</link>
		<comments>http://www.clientcide.com/3rd-party-libraries/moofx/moofx-version-12/#comments</comments>
		<pubDate>Fri, 10 Feb 2006 19:38:46 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[moo.fx]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=18</guid>
		<description><![CDATA[Moo.fx, the tiny Ajax library, has a new release.
There are just a few changes (as befits Moo) such as:
moo.fx changelog:

I&#8217;ve moved the animation logic, now you can use custom transitions (found in the bottom of both moo.fx and moo.fx.pack).
Opacity effect has been modified, works better in safari and now you can call the setOpacity method [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/3rd-party-libraries/moofx/moofx-version-12/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Some examples of 3rd party scripts in use on Download.com</title>
		<link>http://www.clientcide.com/code-snippets/visual-effects/some-examples-of-3rd-party-scripts-in-use-on-downloadcom/</link>
		<comments>http://www.clientcide.com/code-snippets/visual-effects/some-examples-of-3rd-party-scripts-in-use-on-downloadcom/#comments</comments>
		<pubDate>Thu, 09 Feb 2006 18:59:04 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Examples]]></category>
		<category><![CDATA[Organizing Code]]></category>
		<category><![CDATA[Visual Effects]]></category>
		<category><![CDATA[moo.fx]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=17</guid>
		<description><![CDATA[Eric&#8217;s comments regarding the use of 3rd party libraries and my response got me thinking that I should post a few examples of what we&#8217;ve been doing at Download.com. My only caveat is that I&#8217;m probably the person most responsible for this policy as I push for functionality that necessitates their use.
Overlib (http://www.bosrup.com/web/overlib/)

Overlib is a [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/visual-effects/some-examples-of-3rd-party-scripts-in-use-on-downloadcom/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

