<?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: YUI Theater: BayJax Tech Talks from  Nicholas Zakas, Isaac Schlueter, and Matt Hackett</title>
	<atom:link href="http://www.yuiblog.com/blog/index.php/2009/09/17/video-bayjax-sept-09/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yuiblog.com/blog/2009/09/17/video-bayjax-sept-09/</link>
	<description>The official blog of the YUI Project.</description>
	<lastBuildDate>Thu, 09 Feb 2012 01:46:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Remo Brunschwiler</title>
		<link>http://www.yuiblog.com/blog/2009/09/17/video-bayjax-sept-09/comment-page-1/#comment-586483</link>
		<dc:creator>Remo Brunschwiler</dc:creator>
		<pubDate>Sat, 21 Nov 2009 08:31:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.yuiblog.com/blog/?p=493#comment-586483</guid>
		<description>ID&#039;s have the disadvantage of uniqueness. Because I wanted to be able to use the same module more than once on one page, I decided to go with classes (despite of the minimal performance loss). I will soon be ready for a first release of the framework. Would be great if you found the time to have a look.</description>
		<content:encoded><![CDATA[<p>ID&#8217;s have the disadvantage of uniqueness. Because I wanted to be able to use the same module more than once on one page, I decided to go with classes (despite of the minimal performance loss). I will soon be ready for a first release of the framework. Would be great if you found the time to have a look.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicholas C. Zakas</title>
		<link>http://www.yuiblog.com/blog/2009/09/17/video-bayjax-sept-09/comment-page-1/#comment-586375</link>
		<dc:creator>Nicholas C. Zakas</dc:creator>
		<pubDate>Tue, 17 Nov 2009 18:28:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.yuiblog.com/blog/?p=493#comment-586375</guid>
		<description>@Preston - The definition of scalable is &quot;capable of being easily expanded or upgraded on demand&quot;, which I believe fits this approach very well.

@Remo - That&#039;s a fine way of determining which modules to register. You might also want to consider using the element&#039;s ID as a way to do the same.</description>
		<content:encoded><![CDATA[<p>@Preston &#8211; The definition of scalable is &#8220;capable of being easily expanded or upgraded on demand&#8221;, which I believe fits this approach very well.</p>
<p>@Remo &#8211; That&#8217;s a fine way of determining which modules to register. You might also want to consider using the element&#8217;s ID as a way to do the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Remo Brunschwiler</title>
		<link>http://www.yuiblog.com/blog/2009/09/17/video-bayjax-sept-09/comment-page-1/#comment-586372</link>
		<dc:creator>Remo Brunschwiler</dc:creator>
		<pubDate>Tue, 17 Nov 2009 17:12:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.yuiblog.com/blog/?p=493#comment-586372</guid>
		<description>I started to develop a &quot;scalable application architecture&quot; a few months ago. Your speech has pointed out that i&#039;m on the right way. Moreover it has given me some further inspiration for the javascript part. Thank you!
Where my approach differs the most from yours, is that my html/css is based on OOCSS. Because all modules have a .mod and a .mod{moduleName} class, i&#039;m able to automatically register all modules on the page by using this classes to instantiate the appropriate module (ie. new Nx.Module.{moduleName}()).
What do you think about this approach?</description>
		<content:encoded><![CDATA[<p>I started to develop a &#8220;scalable application architecture&#8221; a few months ago. Your speech has pointed out that i&#8217;m on the right way. Moreover it has given me some further inspiration for the javascript part. Thank you!<br />
Where my approach differs the most from yours, is that my html/css is based on OOCSS. Because all modules have a .mod and a .mod{moduleName} class, i&#8217;m able to automatically register all modules on the page by using this classes to instantiate the appropriate module (ie. new Nx.Module.{moduleName}()).<br />
What do you think about this approach?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bayjax: Scalable JavaScript &#124; Engineering Blog - Genius.com Marketing SaaS</title>
		<link>http://www.yuiblog.com/blog/2009/09/17/video-bayjax-sept-09/comment-page-1/#comment-584758</link>
		<dc:creator>Bayjax: Scalable JavaScript &#124; Engineering Blog - Genius.com Marketing SaaS</dc:creator>
		<pubDate>Wed, 23 Sep 2009 18:33:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.yuiblog.com/blog/?p=493#comment-584758</guid>
		<description>[...] for Web Developers. The full slides to the talk can be found at SlideShare, which can accompany the video of the talk available at the YUI [...]</description>
		<content:encoded><![CDATA[<p>[...] for Web Developers. The full slides to the talk can be found at SlideShare, which can accompany the video of the talk available at the YUI [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Preston L. Bannister</title>
		<link>http://www.yuiblog.com/blog/2009/09/17/video-bayjax-sept-09/comment-page-1/#comment-584757</link>
		<dc:creator>Preston L. Bannister</dc:creator>
		<pubDate>Wed, 23 Sep 2009 17:00:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.yuiblog.com/blog/?p=493#comment-584757</guid>
		<description>A better title would be:
 &quot;Composable JavaScript Application Architecture&quot;
or:
 &quot;Modular JavaScript Application Architecture&quot;

The term &quot;scalable&quot; is more usual for topics tied to performance.</description>
		<content:encoded><![CDATA[<p>A better title would be:<br />
 &#8220;Composable JavaScript Application Architecture&#8221;<br />
or:<br />
 &#8220;Modular JavaScript Application Architecture&#8221;</p>
<p>The term &#8220;scalable&#8221; is more usual for topics tied to performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henry Ho</title>
		<link>http://www.yuiblog.com/blog/2009/09/17/video-bayjax-sept-09/comment-page-1/#comment-584654</link>
		<dc:creator>Henry Ho</dc:creator>
		<pubDate>Fri, 18 Sep 2009 01:45:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.yuiblog.com/blog/?p=493#comment-584654</guid>
		<description>found it: 
http://www.slideshare.net/nzakas/scalable-javascript-application-architecture</description>
		<content:encoded><![CDATA[<p>found it:<br />
<a href="http://www.slideshare.net/nzakas/scalable-javascript-application-architecture" rel="nofollow">http://www.slideshare.net/nzakas/scalable-javascript-application-architecture</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henry Ho</title>
		<link>http://www.yuiblog.com/blog/2009/09/17/video-bayjax-sept-09/comment-page-1/#comment-584653</link>
		<dc:creator>Henry Ho</dc:creator>
		<pubDate>Fri, 18 Sep 2009 01:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.yuiblog.com/blog/?p=493#comment-584653</guid>
		<description>“Scalable JavaScript Application Architecture” slides available anywhere? can&#039;t read the demo code...</description>
		<content:encoded><![CDATA[<p>“Scalable JavaScript Application Architecture” slides available anywhere? can&#8217;t read the demo code&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

