blocks|key|605955|text|我会选择jQuery+MVC|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|605956|entityMap|0|LINK|mutability|MUTABLE|url|http://welcome.totheinter.net/tutorials/model-view-controller-in-jquery/^0|4|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I would go with <a href="http://welcome.totheinter.net/tutorials/model-view-controller-in-jquery/" rel="nofollow noreferrer">jQuery MVC</a>

blocks|key|1350409|text|查看http://bennadel.com/projects/cormvc-jquery-framework.htm+Ben是相当敏锐的，如果你深入他的博客，他有一些很好的帖子，关于CorMVC是如何组合在一起的以及为什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1350410|entityMap|0|LINK|mutability|MUTABLE|url|http://bennadel.com/projects/cormvc-jquery-framework.htm^0|2|1K|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Check out <a href="http://bennadel.com/projects/cormvc-jquery-framework.htm" rel="nofollow noreferrer">http://bennadel.com/projects/cormvc-jquery-framework.htm</a> Ben is pretty sharp and if you dig around on his blog he has some nice posts about how CorMVC is put together and why.

blocks|key|2178177|text|你可以使用javascript+MVC框架http://javascriptmvc.com/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2178178|entityMap|0|LINK|mutability|MUTABLE|url|http://javascriptmvc.com/^0|L|P|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You can use javascript MVC framework <a href="http://javascriptmvc.com/" rel="nofollow noreferrer">http://javascriptmvc.com/</a>

blocks|key|2178251|text|我构建应用程序的方式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2178252|2178253|ExtJS框架，单页面应用程序，在单独的JS文件中定义的每个组件，加载的on-demand|unordered-list-item|2178254|Every组件联系它自己的专用web服务(有时不止一个)，将数据提取到ExtJS存储区或特殊用途的数据结构|2178255|渲染使用标准ExtJS组件，因此我可以将存储区绑定到网格，从记录加载表单，...|2178256|2178257|只需选择javascript框架，并遵循其最佳实践即可。我最喜欢的是ExtJS和GWT，但是YMMV。|2178258|不要为此推出您自己的解决方案。复制现代javascript框架所需的工作量太大了。适应现有的东西总是比从头开始构建要快得多。|2178259|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|U|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

The way I build apps:

<ul>
<li>ExtJS framework, single page app, every component defined in a separate JS file, loaded on-demand</li>
<li>Every component contacts its own dedicated web service (sometimes more than one), fetching data into ExtJS stores or special-purpose data structures</li>
<li>The rendering uses standard ExtJS components, so I can bind stores to grids, load forms from records, ...</li>
</ul>

Just choose a javascript framework, and follow its best practices. My favorites are ExtJS and GWT, but YMMV.

Do NOT roll your own solution for this. The effort required to duplicate what modern javascript frameworks do is too big. It is always faster to adapt something existing than to build it all from scratch.

blocks|key|2178352|text|PureMVC/JS的MVC架构是国际海事组织中最优雅的架构。我从中学到了很多。我还发现Nicholas+Zakas的Scalable+JavaScript+Application+Architecture对研究客户端架构选项很有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2178353|另外两个技巧|2178354|2178355|我发现在单页web应用程序中，视图、焦点和输入管理是需要特别注意的领域。|ordered-list-item|2178356|我还发现，抽象JS库很有帮助，可以随时更改您使用的内容，或者在需要时进行混合和匹配。|2178357|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/PureMVC/puremvc-js-multicore-framework/wiki|1|http://www.youtube.com/watch?v=vXjVFPosQHw^0|0|A|0|1N|18|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]|$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|13|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|14|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|O|P|Q|C|$R|U]]]]

MVC architecture of <a href="https://github.com/PureMVC/puremvc-js-multicore-framework/wiki" rel="nofollow noreferrer">PureMVC/JS</a> is the most elegant IMO. I learned a lot from it. I also found <a href="http://www.youtube.com/watch?v=vXjVFPosQHw" rel="nofollow noreferrer">Scalable JavaScript Application Architecture</a> by Nicholas Zakas helpful in researching client side architecture options.

Two other tips 

<ol>
<li>I've found view, focus, and input management are areas that need special attention in single page web apps </li>
<li>I also found it helpful to abstract away the JS library, leaving door open to change mind on what you use, or mix &amp; match should the need arise.</li>
</ol>

blocks|key|606077|text|我目前正在开发的web应用程序使用的是JQuery，我不建议将其用于任何大型的单页面web应用程序。大多数框架，例如Dojo，雅虎，谷歌和其他公司在他们的库中使用名称空间，但JQuery没有，这是一个重大的缺点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|606078|如果你的网站是小的，那么JQuery是可以的，但是如果你打算构建一个大的网站，那么我建议你看看所有可用的Javascript框架，并决定哪一个最能满足你的需求。|606079|我建议将MVC模式应用于javascript/html，也许您的javascript的大多数对象模型都可以作为json来完成，您实际上是通过ajax从服务器返回的，javascirpt使用json来呈现html。|606080|我建议您阅读Ajax+in+action这本书，因为它涵盖了您需要了解的大部分内容。|606081|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

The web application that I am currently working on uses JQuery and I would not recommend it for any large single page web application. Most frameworks i.e. Dojo, yahoo, google and others use namespaces in their libraries but JQuery does not and this is a significant drawback.

If your web site is intended to be small then JQuery would be ok but if you intended to build a large site then I would recommend looking at all the Javascript frameworks available and deciding which one most meets your needs.

And I would recommend applying the MVC pattern to your javascript/html and probably most of your object model for the javascript could be done as the json that you actually return from the server through ajax and the javascirpt uses the json to render html.

I would recommend reading the book Ajax in action as it covers most of the stuff you will need to know.

blocks|key|2178480|text|另类选择:看看ItsNat|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2178481|在JavaScript中思考，但在服务器中使用相同的DOM在Java语言中编写相同的代码，在服务器中更容易管理您的应用程序，而无需自定义客户端/桥，因为UI和数据是在一起的。|2178482|entityMap|0|LINK|mutability|MUTABLE|url|http://www.itsnat.org/^0|7|6|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Alternative: take a look to <a href="http://www.itsnat.org" rel="nofollow">ItsNat</a>

Think in JavaScript but code the same in Java in server with the same DOM APIs, in server is way easier to manage your application without custom client/bridges because UI and data are together.

blocks|key|607666|text|或者看看https://github.com/flosse/scaleApp|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|607667|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/flosse/scaleApp^0|4|Y|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Or have a look at <a href="https://github.com/flosse/scaleApp" rel="nofollow">https://github.com/flosse/scaleApp</a>

blocks|key|1354627|text|我在几个单页面应用程序中成功地使用了Samm.js|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1354628|entityMap|0|LINK|mutability|MUTABLE|url|http://sammyjs.org/^0|I|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I'm using <a href="http://sammyjs.org/" rel="nofollow">Samm.js</a> in several one page applications with great success

blocks|key|607707|text|Nicholas+Zakas由Dean分享的演示文稿是一个非常好的起点。有一段时间，我也在努力回答同样的问题。在做了几个大规模的Javascript产品之后，我想把这些经验分享作为一个参考架构，以防有人需要它。看一看：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|607708|http://boilerplatejs.org/|offset|length|607709|它解决了常见的Javascript开发问题，例如：|607710|607711|Solution+structuring|unordered-list-item|607712|Creating复杂模块层次结构|607713|自包含UI组件|607714|基于事件的模块间通信|607715|路由、历史记录、书签|607716|<代码>H112单元测试|607717|Localization+<代码>H215<代码>H116文档生成<代码>H217<代码>F218|607718|607719|等。|607720|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|P|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@$D|19|E|1A|1|1B]]|A|$]]|$1|F|3|G|5|6|7|1C|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1E|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|1F|8|@]|9|@]|A|$]]|$1|N|3|O|5|K|7|1G|8|@]|9|@]|A|$]]|$1|P|3|Q|5|K|7|1H|8|@]|9|@]|A|$]]|$1|R|3|S|5|K|7|1I|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1J|8|@]|9|@]|A|$]]|$1|V|3|W|5|K|7|1K|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1M|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|C]]]]

Nicholas Zakas's presentation as shared by Dean is a very good place to start with. I was also struggling to answer the same question for a while. After doing couple of large scale Javascript products, thought of sharing the learnings as a reference architecture in case someone needs it. Have a look at:

<a href="http://boilerplatejs.org/" rel="nofollow">http://boilerplatejs.org/</a>

It addresses common Javascript development concerns such as:

<ul>
<li>Solution structuring</li>
<li>Creating complex module hierarchy </li>
<li>Self contained UI components </li>
<li>Event based inter module communication </li>
<li>Routing, History, Bookmarking </li>
<li>Unit Testing </li>
<li>Localization </li>
<li>Document Generation</li>
</ul>

etc.

blocks|key|606174|text|最好的做法是查看其他框架的示例用法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|606175|展示了许多许多SPA框架。|606176|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The best thing to do is to look at example uses of other frameworks:

<a href="http://addyosmani.github.com/todomvc/" rel="nofollow">TodoMVC</a> showcases many many SPA frameworks.

blocks|key|3585647|text|允许您创建单页面应用程序。还允许你编写超文本标记语言，CSS+(SASS)，JavaScript到单独的文件，并在最后将它们捆绑到一个输出文件中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3585648|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

<a href="http://nikaframework.com" rel="nofollow" title="NikaFramework">NikaFramework</a> allows you to create single-page application. Also allows you to write HTML, CSS (SASS), JavaScript into separate files and bundle them into only one output file in the end.

blocks|key|2178709|text|Question+-+What+makes+an+application+complex+?+|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2178710|答案--在问题本身中使用“复杂”一词。因此，一个共同的趋势是从一开始就寻找复杂的解决方案。|unstyled|2178711|Question+-+What+does+the+word+complex+means+?|2178712|答案--任何未知或部分理解的东西。即使在今天，地心引力理论对我来说也很复杂，但对1655年发现它的艾萨克·牛顿爵士来说却并非如此。|2178713|Question+-+What+tools+can+I+use+to+deal+with+complexity+?|2178714|答案-理解和简单。|2178715|Question+-+But+I+understand+my+application+.+Its+still+complex+?|2178716|答案-三思而后行，因为理解和复杂性并不是共存的。如果你理解一个巨大的应用程序，我相信你会同意它只是一个小的和简单的单元的集成。|2178717|Question+-+Why+all+of+the+above+philosophical+discussion+for+a+question+on+
+++++++++++Single+Page+Application+(SAP)?|2178718|答案-因为，|2178719|->+SPA不是某种新发明的核心技术，我们在应用程序开发中所做的许多事情都需要重新发明轮子。|2178720|->的概念是出于对web应用程序更好的性能、可用性、可扩展性和可维护性的需求。|2178721|->是一种相当新的设计模式，因此将其理解为一种设计模式对制定关于SPA架构的明智决策大有裨益。|2178722|在根级别的->没有SPA是复杂的，因为在理解了应用程序和SPA模式的需求之后，您将意识到您仍然在创建应用程序，几乎与您之前在开发方法中进行了一些修改和重新安排的方式相同。|2178723|Question+-+What+about+the+use+of+Frameworks+?|2178724|答案-框架是一些常见的通用模式的样板代码/解决方案，因此它们可以从应用程序开发中减少x%25+(变量，基于应用程序)的负载，但是对于繁重和不断增长的应用程序来说，不应该对它们有太多的期望。完全控制你的应用程序结构和流程，但最重要的是控制它的代码，这总是一个很好的例子。应用程序代码中不应该有灰色或黑色区域。|2178725|Question+-+Can+you+suggest+one+of+the+many+approaches+to+SPA+architecture+?|2178726|答案-根据应用程序的性质考虑您自己的框架。对应用程序组件分类。寻找一个与你的派生框架接近的现有框架，如果你找到了它就使用它，如果你找不到它，那么我建议你继续使用你自己的框架。创建框架是一项前期的工作，但从长远来看会产生更好的结果。我的SPA框架中的一些基本组件包括：|2178727|2178728|数据源:用于显示数据的模型/模型集合|unordered-list-item|2178729|标记:+Templates|2178730|Interaction+|2178731|应用程序:Events|2178732|状态捕获和导航:+Routing|2178733|Utilities、小部件和插件:+libraries|2178734|2178735|让我知道这是否有任何帮助，并祝您的架构好运!!|offset|length|style|BOLD|2178736|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|H|6|0^^$0|@$1|2|3|4|5|6|7|1Z|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|20|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|21|8|@]|9|@]|A|$B|C]]|$1|I|3|J|5|F|7|22|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|23|8|@]|9|@]|A|$B|C]]|$1|M|3|N|5|F|7|24|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|25|8|@]|9|@]|A|$B|C]]|$1|Q|3|R|5|F|7|26|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|27|8|@]|9|@]|A|$B|C]]|$1|U|3|V|5|F|7|28|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|29|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|F|7|2A|8|@]|9|@]|A|$]]|$1|10|3|11|5|F|7|2B|8|@]|9|@]|A|$]]|$1|12|3|13|5|F|7|2C|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|2D|8|@]|9|@]|A|$B|C]]|$1|16|3|17|5|F|7|2E|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|2F|8|@]|9|@]|A|$B|C]]|$1|1A|3|1B|5|F|7|2G|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|F|7|2H|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|1F|7|2I|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|1F|7|2J|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|1F|7|2K|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|1F|7|2L|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|1F|7|2M|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|1F|7|2N|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|F|7|2O|8|@]|9|@]|A|$]]|$1|1R|3|1S|5|F|7|2P|8|@$1T|2Q|1U|2R|1V|1W]]|9|@]|A|$]]|$1|1X|3|-4|5|F|7|2S|8|@]|9|@]|A|$]]]|1Y|$]]

<pre><code>Question - What makes an application complex ? 
</code></pre>

Answer - The use of word 'complex' in the question itself. Hence, a common tendency will be to look out for a complex solution right from the beginning. 

<pre><code>Question - What does the word complex means ?
</code></pre>

Answer - Anything that is unknown or partially understood. Example : The theory of Gravity even today is COMPLEX to me but not to Sir Isaac Newton who discovered it in 1655.

<pre><code>Question - What tools can I use to deal with complexity ?
</code></pre>

Answer - Understanding and simplicity.

<pre><code>Question - But I understand my application . Its still complex ?
</code></pre>

Answer - Think twice, because understanding and complexity does not co-exist. If you understand a huge huge application, I am sure you will agree that it is nothing but an integration of small and simple units.

<pre><code>Question - Why all of the above philosophical discussion for a question on 
 Single Page Application (SAP)?
</code></pre>

Answer - Because, 

-> SPA is not some kind of core technology that is newly invented for which we need to reinvent the wheel for a lot of things that we are doing in application development. 

-> Its a concept driven by the need for better performance, availability, scalability and maintainability of web applications. 

-> Its a fairly newly identified design pattern, so an understanding of SPA as a design pattern goes long way in making informed decisions about the architecture of a SPA. 

-> At the root level no SPA is complex, because after understanding the needs of an application and the SPA pattern, you will realize that you are still creating an application, pretty much the same way you did before with some modifications and re-arrangements in the development approach.

<pre><code>Question - What about the use of Frameworks ?
</code></pre>

Answer - Frameworks are boiler plate code / solution for some commonly identified and generic patterns, hence they can take off x% (variable, based on the application) load from application development but then not a lot should be expected out of them specially for heavy and growing applications. Its always a good case to be in complete control of your application structure and flow but most importantly the code for it. There should be no grey or black areas in the application code.

<pre><code>Question - Can you suggest one of the many approaches to SPA architecture ?
</code></pre>

Answer - Think of your own framework based on the nature of your application. Categorize application components. Look for an existing framework that is close to your derived framework, if you find it then use it, if you do not find it then I suggest going ahead with your own. Creating framework is quite an effort upfront but produces better results in long run. Some basic components in my SPA framework will be:

<ul>
<li>Data Source : Models / Collections of Models</li>
<li>Mark Up for presenting data : Templates</li>
<li>Interaction with the application : Events</li>
<li>State capturing and navigation : Routing</li>
<li>Utilities , widgets and plug-ins : libraries</li>
</ul>

Let me know if this helped in any way and good luck with your SPA architecture !!

blocks|key|1350711|text|我建议你探索一下Yeoman。它允许您为新项目使用现有“最佳实践”。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1350712|例如：|1350713|如果你决定使用Angular.js，有一个Yeoman+generator，它为你提供了一个路由，视图，服务等的结构，还允许你测试，缩减你的代码等。|1350714|如果您决定使用Backbone，请查看this+generator|1350715|entityMap|0|LINK|mutability|MUTABLE|url|http://yeoman.io/|1|https://github.com/yeoman/generator-angular|2|https://github.com/yeoman/generator-backbone^0|8|6|0|0|0|L|G|1|0|J|E|2|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|J|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]|T|$5|M|N|O|C|$P|U]]]]

I would recommend to explore <a href="http://yeoman.io/" rel="nofollow">Yeoman</a>. It allow you to use existing "best practice" for your new project.

For example: 

if you decide to use Angular.js, there is a <a href="https://github.com/yeoman/generator-angular" rel="nofollow">Yeoman generator</a>, that give you a structure for routing, views, services, etc. Also allow you to Test, minify your code, etc.

If you decide to use Backbone, checkout <a href="https://github.com/yeoman/generator-backbone" rel="nofollow">this generator</a>

How should a complex single-page JS web application be structured on the client-side? Specifically I'm curious about how to cleanly structure the application in terms of its model objects, UI components, any controllers, and objects handling server persistence.

MVC seemed like a fit at first. But with UI components nested at various depths (each with their own way of acting on/reacting to model data, and each generating events which they themselves may or may not handle directly), it doesn't seem like MVC can be cleanly applied. (But please correct me if that's not the case.)

--

(<a href="https://stackoverflow.com/questions/2529722/suggestions-for-single-page-web-application-design">This question</a> resulted in two suggestions of using ajax, which is obviously needed for anything other than the most trivial one-page app.)

Architecture of a single-page JavaScript web application?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如何在客户端构建一个复杂的单页面JS web应用程序？具体地说，我很好奇如何根据模型对象、UI组件、任何控制器和处理服务器持久性的对象来整洁地构造应用程序。一开始，MVC看起来很合适。但是，由于UI组件嵌套在不同的深度(每个组件都有自己的方式作用于模型数据/反应模型数据，并且每个组件都生成自己可能直接处理也可能不直接处...

问单页JavaScript web应用程序的体系结构？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问单页JavaScript web应用程序的体系结构？EN