<?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: Web Application Architecture with ExtJS</title>
	<atom:link href="http://www.akawebdesign.com/2010/06/23/web-application-architecture-with-extjs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.akawebdesign.com/2010/06/23/web-application-architecture-with-extjs/</link>
	<description>Longtime nerd. Rockstar developer.</description>
	<lastBuildDate>Tue, 07 Feb 2012 08:33:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Arthur Kay</title>
		<link>http://www.akawebdesign.com/2010/06/23/web-application-architecture-with-extjs/#comment-322</link>
		<dc:creator>Arthur Kay</dc:creator>
		<pubDate>Mon, 16 May 2011 16:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.akawebdesign.com/?p=481#comment-322</guid>
		<description>It completely depends on your application.

If you are using a JS framework like ExtJS, it is unlikely you&#039;ll ever have a true &quot;View&quot; rendered by a controller because the framework is used to build the UI components.

On the other hand, you might have situations where you actually want a View (or Partial View) rendered directly into the DOM.

In most of my ExtJS and Sencha Touch applications, I only use the &quot;Index&quot; view to launch my JS code (for example, creating an ExtJS Viewport to encompass the UI), also possibly injecting preliminary data via ASP.NET (or PHP, or whatever).

Even though we may be using an MVC approach to our backend, our AJAX applications won&#039;t rely on traditional MVC Views.

ExtJS 4.0 actually takes this idea to the next level. If you haven&#039;t done so already, I suggest reading the &lt;a href=&quot;http://dev.sencha.com/deploy/ext-4.0-beta3/docs/guide/application_architecture.html&quot; rel=&quot;nofollow&quot;&gt;MVC guide&lt;/a&gt; in the ExtJS 4.0 documentation.</description>
		<content:encoded><![CDATA[<p>It completely depends on your application.</p>
<p>If you are using a JS framework like ExtJS, it is unlikely you&#8217;ll ever have a true &#8220;View&#8221; rendered by a controller because the framework is used to build the UI components.</p>
<p>On the other hand, you might have situations where you actually want a View (or Partial View) rendered directly into the DOM.</p>
<p>In most of my ExtJS and Sencha Touch applications, I only use the &#8220;Index&#8221; view to launch my JS code (for example, creating an ExtJS Viewport to encompass the UI), also possibly injecting preliminary data via ASP.NET (or PHP, or whatever).</p>
<p>Even though we may be using an MVC approach to our backend, our AJAX applications won&#8217;t rely on traditional MVC Views.</p>
<p>ExtJS 4.0 actually takes this idea to the next level. If you haven&#8217;t done so already, I suggest reading the <a href="http://dev.sencha.com/deploy/ext-4.0-beta3/docs/guide/application_architecture.html" rel="nofollow">MVC guide</a> in the ExtJS 4.0 documentation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://www.akawebdesign.com/2010/06/23/web-application-architecture-with-extjs/#comment-321</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Mon, 16 May 2011 01:54:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.akawebdesign.com/?p=481#comment-321</guid>
		<description>So I have customers, purchase orders, ar, ap, etc. then all are under _app.  There never will be an &quot;index&quot; or page rendered by any controller (other than the start), just json correct?</description>
		<content:encoded><![CDATA[<p>So I have customers, purchase orders, ar, ap, etc. then all are under _app.  There never will be an &#8220;index&#8221; or page rendered by any controller (other than the start), just json correct?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arthur Kay</title>
		<link>http://www.akawebdesign.com/2010/06/23/web-application-architecture-with-extjs/#comment-320</link>
		<dc:creator>Arthur Kay</dc:creator>
		<pubDate>Mon, 16 May 2011 01:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.akawebdesign.com/?p=481#comment-320</guid>
		<description>I would probably only have one &quot;_app&quot; for most projects, but it&#039;s possible you could have multiple interfaces using the same backend.

For example, you might have a desktop UI and a mobile UI... others are possible as well.

Lastly, the &quot;_app&quot; is the encompassing UI, which interacts with any number of your controllers. Does that answer your question?</description>
		<content:encoded><![CDATA[<p>I would probably only have one &#8220;_app&#8221; for most projects, but it&#8217;s possible you could have multiple interfaces using the same backend.</p>
<p>For example, you might have a desktop UI and a mobile UI&#8230; others are possible as well.</p>
<p>Lastly, the &#8220;_app&#8221; is the encompassing UI, which interacts with any number of your controllers. Does that answer your question?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://www.akawebdesign.com/2010/06/23/web-application-architecture-with-extjs/#comment-319</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Sun, 15 May 2011 16:08:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.akawebdesign.com/?p=481#comment-319</guid>
		<description>Using asp.net mvc how many Ext &quot;apps&quot; do you have?  i.e. is there just one for everything or one for each controller or logical grouping?</description>
		<content:encoded><![CDATA[<p>Using asp.net mvc how many Ext &#8220;apps&#8221; do you have?  i.e. is there just one for everything or one for each controller or logical grouping?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arthur Kay</title>
		<link>http://www.akawebdesign.com/2010/06/23/web-application-architecture-with-extjs/#comment-108</link>
		<dc:creator>Arthur Kay</dc:creator>
		<pubDate>Thu, 09 Sep 2010 15:20:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.akawebdesign.com/?p=481#comment-108</guid>
		<description>Victor,

That&#039;s a good question, and I don&#039;t really have a definitive answer for you.

My understanding of &quot;Views&quot; in MVC is that they&#039;re bound to the &quot;Controllers&quot;. Thus if you had a &quot;Home&quot; controller, you might have an &quot;Index&quot; view at /Home/Index. 

Because our JavaScript code isn&#039;t bound to the controllers I (personally) wouldn&#039;t put the JS inside the &quot;Views&quot; folder. Views also typically contain server-side code (in your case, PHP) so separating server-side and client-side functionality makes sense to me.

On the other hand, Views do contain presentation functionality - so you could put your JS code in a Views/Shared folder.

Another concern I would have relates to &quot;Areas&quot; in MVC (I use ASP.NET MVC, so I can&#039;t speak specifically about DooPHP). Because we might have many &quot;Areas&quot; in our application, we may want all of our JS code globally accessible. In that case, it wouldn&#039;t make sense to have our JavaScript code inside a &quot;Views&quot; folder because those views are specific to the containing area.

I suppose it&#039;s all a matter of preference.</description>
		<content:encoded><![CDATA[<p>Victor,</p>
<p>That&#8217;s a good question, and I don&#8217;t really have a definitive answer for you.</p>
<p>My understanding of &#8220;Views&#8221; in MVC is that they&#8217;re bound to the &#8220;Controllers&#8221;. Thus if you had a &#8220;Home&#8221; controller, you might have an &#8220;Index&#8221; view at /Home/Index. </p>
<p>Because our JavaScript code isn&#8217;t bound to the controllers I (personally) wouldn&#8217;t put the JS inside the &#8220;Views&#8221; folder. Views also typically contain server-side code (in your case, PHP) so separating server-side and client-side functionality makes sense to me.</p>
<p>On the other hand, Views do contain presentation functionality &#8211; so you could put your JS code in a Views/Shared folder.</p>
<p>Another concern I would have relates to &#8220;Areas&#8221; in MVC (I use ASP.NET MVC, so I can&#8217;t speak specifically about DooPHP). Because we might have many &#8220;Areas&#8221; in our application, we may want all of our JS code globally accessible. In that case, it wouldn&#8217;t make sense to have our JavaScript code inside a &#8220;Views&#8221; folder because those views are specific to the containing area.</p>
<p>I suppose it&#8217;s all a matter of preference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victor Cardins</title>
		<link>http://www.akawebdesign.com/2010/06/23/web-application-architecture-with-extjs/#comment-107</link>
		<dc:creator>Victor Cardins</dc:creator>
		<pubDate>Thu, 09 Sep 2010 14:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.akawebdesign.com/?p=481#comment-107</guid>
		<description>Hi Arthur,

Thanks a ton ! This post was my start point for building my first Ext professional application. I still have a concern. I have used a MVC php framework - DooPhp and I was wondering if instead the _apps/js folder, the presentstion javascript shouldn&#039;t be within the view folder ?

root
+ global
  + css
  + ext
  + js ( common js) 
+ controller
+ model
+ view
  + user  ( JSs for presenting User related information)
  + order ( JSs for presenting Order related information)
...

I appreciate your attention !</description>
		<content:encoded><![CDATA[<p>Hi Arthur,</p>
<p>Thanks a ton ! This post was my start point for building my first Ext professional application. I still have a concern. I have used a MVC php framework &#8211; DooPhp and I was wondering if instead the _apps/js folder, the presentstion javascript shouldn&#8217;t be within the view folder ?</p>
<p>root<br />
+ global<br />
  + css<br />
  + ext<br />
  + js ( common js)<br />
+ controller<br />
+ model<br />
+ view<br />
  + user  ( JSs for presenting User related information)<br />
  + order ( JSs for presenting Order related information)<br />
&#8230;</p>
<p>I appreciate your attention !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sanel</title>
		<link>http://www.akawebdesign.com/2010/06/23/web-application-architecture-with-extjs/#comment-106</link>
		<dc:creator>Sanel</dc:creator>
		<pubDate>Mon, 28 Jun 2010 13:31:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.akawebdesign.com/?p=481#comment-106</guid>
		<description>Hi Arthur

This is very useful post. It will help me a lot. Thanks</description>
		<content:encoded><![CDATA[<p>Hi Arthur</p>
<p>This is very useful post. It will help me a lot. Thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>

