<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Storage and Javascript</title>
	<atom:link href="http://bencrowder.net/blog/2006/06/storage-and-javascript/feed/" rel="self" type="application/rss+xml" />
	<link>http://bencrowder.net/blog/2006/06/storage-and-javascript/</link>
	<description>The personal website of Ben Crowder</description>
	<lastBuildDate>Thu, 11 Mar 2010 05:09:37 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jonathan Aquino</title>
		<link>http://bencrowder.net/blog/2006/06/storage-and-javascript/#comment-122</link>
		<dc:creator>Jonathan Aquino</dc:creator>
		<pubDate>Sun, 11 Jun 2006 07:44:54 +0000</pubDate>
		<guid isPermaLink="false">http://outsidethebox.blankslate.net/2006/06/07/storage-and-javascript/#comment-122</guid>
		<description>Hi Ben - I loved Prototype, but am currently working with Dojo and would miss a lot of things from it (for largish Javascript projects). Three things:

(1) the &quot;require&quot; statement for including neighbouring Javascript files, facilitating the organization of a Javascript project into one-class-per-file

(2) the Widget superclass, for modularizing GUI elements into reusable panels/widgets (widget = html + javascript)

(3) the dojo.io.connect() function that lets me hook into any function call -- before it, after it, around it.


That said, it&#039;s probably overkill for more traditional websites. So I think I&#039;ll probably go Prototype for traditional sites, Dojo for richer, more javascript-heavy sites.</description>
		<content:encoded><![CDATA[<p>Hi Ben &#8211; I loved Prototype, but am currently working with Dojo and would miss a lot of things from it (for largish Javascript projects). Three things:</p>
<p>(1) the &#8220;require&#8221; statement for including neighbouring Javascript files, facilitating the organization of a Javascript project into one-class-per-file</p>
<p>(2) the Widget superclass, for modularizing GUI elements into reusable panels/widgets (widget = html + javascript)</p>
<p>(3) the dojo.io.connect() function that lets me hook into any function call &#8212; before it, after it, around it.</p>
<p>That said, it&#8217;s probably overkill for more traditional websites. So I think I&#8217;ll probably go Prototype for traditional sites, Dojo for richer, more javascript-heavy sites.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
