<?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; Event Scripting</title>
	<atom:link href="http://www.clientcide.com/category/code-snippets/event-scripting/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>Confirmer widget</title>
		<link>http://www.clientcide.com/code-snippets/event-scripting/confirmer-widget/</link>
		<comments>http://www.clientcide.com/code-snippets/event-scripting/confirmer-widget/#comments</comments>
		<pubDate>Fri, 09 Mar 2007 01:32:31 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Widgets]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/code-snippets/event-scripting/confirmer-widget/</guid>
		<description><![CDATA[Helping out our CMS group today I hacked out a new little widget class called &#8220;Confirmer&#8221; that handles notifying the user when something they&#8217;ve done on the page requires some sort of notice. An auto-save, or the failure to auto-save, or any other sort of message.
It&#8217;s designed to be unobtrusive so it doesn&#8217;t annoy the [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/event-scripting/confirmer-widget/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mootools Beginner&#8217;s Example</title>
		<link>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-beginners-example/</link>
		<comments>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-beginners-example/#comments</comments>
		<pubDate>Sat, 10 Feb 2007 02:20:56 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Manipulating the Dom]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[Visual Effects]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/code-snippets/manipulating-the-dom/mootools-beginners-example/</guid>
		<description><![CDATA[If you are new to javascript or Mootools, you should:

1) Read the docs
2) Read the Mootools Tutorial
Now, the problem with the Tutorial is that it shows you snippets of how Mootools work, but doesn&#8217;t put them all together to show you how to actually do things on a page.
So in an effort to help people [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-beginners-example/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DomReady, DomPolling, and window.onload revisited</title>
		<link>http://www.clientcide.com/best-practices/optimization/domready-dompolling-and-windowonload-revisited/</link>
		<comments>http://www.clientcide.com/best-practices/optimization/domready-dompolling-and-windowonload-revisited/#comments</comments>
		<pubDate>Mon, 05 Feb 2007 19:34:55 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Optimization]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/best-practices/optimization/domready-dompolling-and-windowonload-revisited/</guid>
		<description><![CDATA[Via Ajaxian is this post revising the age-old window.onload problem. I tried to write a dom polling method that would re-evaluate the dom every few milliseconds maybe 3 or 4 months ago but got distracted. Here&#8217;s the work of smarter and less easily distracted people than I, and it&#8217;s worth reading (even if you skip [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/optimization/domready-dompolling-and-windowonload-revisited/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mootools 1.0 goes gold, CNET Libraries WikiTorial</title>
		<link>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-10-goes-gold-cnet-libraries-wikitorial/</link>
		<comments>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-10-goes-gold-cnet-libraries-wikitorial/#comments</comments>
		<pubDate>Tue, 30 Jan 2007 20:38:19 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[CNET JS Standards]]></category>
		<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Manipulating the Dom]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[Visual Effects]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/code-snippets/manipulating-the-dom/mootools-10-goes-gold-cnet-libraries-wikitorial/</guid>
		<description><![CDATA[Mootools 1.0 is out. Fancy new site design and docs.
We&#8217;ve already refactored all our code for 1.0, though it is not yet released to the CNET site. We&#8217;re entering into QA now&#8230;
I&#8217;ve also released the second part of my wiki tutorial series, this time giving working examples of all the CNET common code. The CNET [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-10-goes-gold-cnet-libraries-wikitorial/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Keywatcher.js &#8211; capture key presses (Mootools)</title>
		<link>http://www.clientcide.com/3rd-party-libraries/keywatcherjs-capture-key-presses-mootools/</link>
		<comments>http://www.clientcide.com/3rd-party-libraries/keywatcherjs-capture-key-presses-mootools/#comments</comments>
		<pubDate>Thu, 23 Nov 2006 18:01:49 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[3rd Party Libraries]]></category>
		<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[MooTools]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/3rd-party-libraries/keywatcherjs-capture-key-presses-mootools/</guid>
		<description><![CDATA[Here&#8217;s a nice little extension I found on the mootools forums. It let&#8217;s you assign an action to any element when the element has focused and the user clicks a key. I haven&#8217;t played around with it yet, but it&#8217;s super small and looks useful for form inputs and whatnot. Credit goes to BlackMac.
/*
Script: keywatcher.js
 [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/3rd-party-libraries/keywatcherjs-capture-key-presses-mootools/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Mootools Primer, CNET Libraries online</title>
		<link>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-primer-cnet-libraries-online/</link>
		<comments>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-primer-cnet-libraries-online/#comments</comments>
		<pubDate>Wed, 22 Nov 2006 20:10:31 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[CNET JS Standards]]></category>
		<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Manipulating the Dom]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[Visual Effects]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/code-snippets/manipulating-the-dom/mootools-primer-cnet-libraries-online/</guid>
		<description><![CDATA[Hi gang,
I&#8217;ve been at work on a mootools primer as a tutorial for those who want to use the library but don&#8217;t know a lot about javascript. It&#8217;s replete with working code examples that you can execute right in the browser and see the result.
I&#8217;m aware that the forthcoming version 1.0 of Mootools contains a [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-primer-cnet-libraries-online/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Mootools and 3rd party widgets</title>
		<link>http://www.clientcide.com/code-snippets/visual-effects/mootools-and-3rd-party-widgets/</link>
		<comments>http://www.clientcide.com/code-snippets/visual-effects/mootools-and-3rd-party-widgets/#comments</comments>
		<pubDate>Thu, 26 Oct 2006 20:51:33 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Visual Effects]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/code-snippets/visual-effects/mootools-and-3rd-party-widgets/</guid>
		<description><![CDATA[I have several classes that I&#8217;ve written for use with Mootools that I&#8217;ll be posting about soon. I thought I&#8217;d go ahead and point to this great little slider widget over at lenhatanh.pebox:

I know that Valerio over at mootools is planning a plugin repository for things like this, which I think will really help move [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/visual-effects/mootools-and-3rd-party-widgets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rewrite of Behaviour.js in the CNET framework (mootools)</title>
		<link>http://www.clientcide.com/best-practices/optimization/rewrite-of-behaviourjs-in-the-cnet-framework/</link>
		<comments>http://www.clientcide.com/best-practices/optimization/rewrite-of-behaviourjs-in-the-cnet-framework/#comments</comments>
		<pubDate>Wed, 27 Sep 2006 01:52:13 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[CNET JS Standards]]></category>
		<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Optimization]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=168</guid>
		<description><![CDATA[Huh. So this was eaiser than I thought.
In the Download.com Watch List profile page we use the Behaviour library to define a bunch of functionality (er, I mean &#8220;I use&#8230;&#8221; as I wrote all this over a year ago). We&#8217;re going to replace Prototype with our new framework (based mostly on Mootools). Behaviour will work [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/optimization/rewrite-of-behaviourjs-in-the-cnet-framework/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>event:Selectors &#8211; Behaviour +</title>
		<link>http://www.clientcide.com/3rd-party-libraries/eventselectors-behaviour/</link>
		<comments>http://www.clientcide.com/3rd-party-libraries/eventselectors-behaviour/#comments</comments>
		<pubDate>Thu, 27 Jul 2006 19:12:56 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[3rd Party Libraries]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Organizing Code]]></category>
		<category><![CDATA[Prototype]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=126</guid>
		<description><![CDATA[I just happened upon event:Selectors. It&#8217;s very similar to Behaviour.js (the author&#8217;s spelling, not mine) in most respects, though its much smaller (72 lines / ~2k) and has some nice added functionality using Prototype shortcuts (Behaviour is stand-alone and duplicates a lot of Prototype stuff and is, therefore, larger).
Basic usage:
var Rules = {
   [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/3rd-party-libraries/eventselectors-behaviour/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A DOM Ready Extension for Prototype</title>
		<link>http://www.clientcide.com/code-snippets/event-scripting/a-dom-ready-extension-for-prototype/</link>
		<comments>http://www.clientcide.com/code-snippets/event-scripting/a-dom-ready-extension-for-prototype/#comments</comments>
		<pubDate>Tue, 11 Jul 2006 19:50:16 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Prototype]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=123</guid>
		<description><![CDATA[Holy cow this is awesome.
via ajaxian: original post
Dean, John, Matthias and a load of other people were working on a really robust solution to the DOM Ready problem. In case you haven&#8217;t seen Dean&#8217;s post, they did it and it is good shit. If you want to read more of an explanation head over to [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/event-scripting/a-dom-ready-extension-for-prototype/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
	</channel>
</rss>

