问题描述
我刚刚为客户启动了一个新的 GWT 项目，我很想了解人们对各种 GWT MVC 架构的体验.在最近的一个项目中，我使用了 GXT MVC，以及自定义消息传递解决方案(基于Appcelerator 的 MQ).GXT MVC 工作正常，但对于 GWT 来说似乎有点过分，而且很难处理浏览器历史记录.我听说过 PureMVC 和 GWTiger，但从未使用过它们.我们的自定义 MQ 解决方案运行良好，但使用 JUnit 测试组件变得困难.
I just started a new GWT project for a client and I'm interested in hearing people's experience with various GWT MVC architectures. On a recent project, I used both GXT MVC, as well as a custom messaging solution (based on Appcelerator's MQ). GXT MVC worked OK, but it seemed like overkill for GWT and was hard to make work with browser history. I've heard of PureMVC and GWTiger, but never used them. Our custom MQ solution worked pretty well, but made it difficult to test components with JUnit.
此外，我听说 Google Wave(一个 GWT 应用程序)是使用模型-视图-展示器模式编写的.最近发布了一个 示例 MVP 应用程序，但查看代码，它没有似乎不那么直观.
In addition, I've heard that Google Wave (a GWT application) is written using a Model-View-Presenter pattern. A sample MVP application was recently published, but looking at the code, it doesn't seem that intuitive.
如果您要构建一个新的 GWT 应用程序，您会使用哪种架构?您选择的利弊是什么?
If you were building a new GWT application, which architecture would you use? What are the pros and cons of your choice?
谢谢，
马特
推荐答案
值得注意的是，google终于写出了使用mvp架构进行设计的教程.它阐明了上面列出的 google i/o 谈话中的许多元素.看一看:https://developers.google.com/web-toolkit/articles/mvp-架构
It's worth noting that google has finally written out a tutorial for designing using the mvp architecture. It clarifies a lot of the elements from the google i/o talk listed above. Take a looK: https://developers.google.com/web-toolkit/articles/mvp-architecture
这篇关于您对构建 GWT 应用程序的建议是什么?MVC、MVP 还是自定义消息传递解决方案?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！