<?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: MochiKit Effects</title>
	<atom:link href="http://www.splee.co.uk/2006/01/19/mochikit-effects/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.splee.co.uk/2006/01/19/mochikit-effects/</link>
	<description>Bring out the g33k</description>
	<pubDate>Thu, 20 Nov 2008 12:24:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Splee</title>
		<link>http://www.splee.co.uk/2006/01/19/mochikit-effects/#comment-1222</link>
		<dc:creator>Splee</dc:creator>
		<pubDate>Tue, 24 Jan 2006 14:43:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.splee.co.uk/2006/01/19/mochikit-effects/#comment-1222</guid>
		<description>I agree, the mochikit effects are currently larger.  What I really mean is that there's no extra overhead for things that *aren't being used*.  

While that doesn't actually amount to the same thing I have no doubt that as development proceeds the MockiKit effects packages will get a lot smaller.</description>
		<content:encoded><![CDATA[<p>I agree, the mochikit effects are currently larger.  What I really mean is that there&#8217;s no extra overhead for things that <em>aren&#8217;t being used</em>.  </p>
<p>While that doesn&#8217;t actually amount to the same thing I have no doubt that as development proceeds the MockiKit effects packages will get a lot smaller.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl G</title>
		<link>http://www.splee.co.uk/2006/01/19/mochikit-effects/#comment-1216</link>
		<dc:creator>Karl G</dc:creator>
		<pubDate>Thu, 19 Jan 2006 17:00:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.splee.co.uk/2006/01/19/mochikit-effects/#comment-1216</guid>
		<description>The port is actually larger than the original scriptaculous library including the overhead of prototype.js. It will eventually be smaller but at the moment New.js implements most of the prototype functionality by copying the appropriate functions out of prototype.js. I've done some work on whittling down New.js but not as much as I'd like. If you're interested in checking out the progress, you can grab a darcs checkout at [1]. This is still a drop in replacement but stuff outside of effects might or might not work.

[1] http://gr.ayre.st/~grayrest/mochi/mochiriffic 

If you're looking for space efficient effects, a mochi port of moofx would probably fit the bill, but it wouldn't be a drop in replacement for Scriptaculous.</description>
		<content:encoded><![CDATA[<p>The port is actually larger than the original scriptaculous library including the overhead of prototype.js. It will eventually be smaller but at the moment New.js implements most of the prototype functionality by copying the appropriate functions out of prototype.js. I&#8217;ve done some work on whittling down New.js but not as much as I&#8217;d like. If you&#8217;re interested in checking out the progress, you can grab a darcs checkout at [1]. This is still a drop in replacement but stuff outside of effects might or might not work.</p>
<p>[1] <a href="http://gr.ayre.st/~grayrest/mochi/mochiriffic" rel="nofollow">http://gr.ayre.st/~grayrest/mochi/mochiriffic</a> </p>
<p>If you&#8217;re looking for space efficient effects, a mochi port of moofx would probably fit the bill, but it wouldn&#8217;t be a drop in replacement for Scriptaculous.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
