GWT mvp:Places、RequestFactory、SmartGwt 和 gwt-sl

发布于 2024-11-05 07:59:08 字数 1126 浏览 0 评论 0 原文

我是 GWT 和 MVP 的新手,并且探索了一些库(gwt-sl、gwt-presenter、gwt-dispatch)和框架(smartgwt ..),但我感到非常困惑。 我决定坚持使用 smartgwt ui 组件和 gwt mvp 来处理它们。 smartgwt 是使用一个数据源建模的,我希望理想地扩展该数据源(并使用 dto 进行填充(或使用 gwt 的请求工厂的代理对象))。然而我现在还没有掌握所有这些。

a) 在 google 列出的 gwt mvp 中,一个地方的状态到底是什么?我们总是派人去一个新地方吗?如果不是,并且历史记录维护位置令牌,那么状态是如何加载的?

b) 来自另一篇关于 gwt mvp 模型在哪里? 我们大多数人习惯于典型的 MVC 设计范例,会假设模型状态存在于演示器中。我想按照建议其他地方 clientfactory 是合适的在存储视图中显示的当前模型的位置?

c) 我想知道是否可以尝试使用 requestfactory 来填充 smartgwt 数据绑定组件? (据我了解,使用 smartgwt 服务器端框架本质上是做同样的事情..仅通过线路传输对象图中的更改?)

d)在 David Chandler 幻灯片的第 47 页,我不太明白所提议的布局。 ( 2 个 placeChangeHandler ?每个活动管理器有 2 组 widgetList ?有人可以解释一下吗?

e)任何人都可以分享他们的经验 gwt-sl (用于服务器端 spring 集成?)

提前感谢所有 gwt 专家

I am new to GWT and MVP and have explored a few libraries (gwt-sl, gwt-presenter,gwt-dispatch) and frameworks (smartgwt ..) and i am getting very confused.
I have decided to stick with using smartgwt ui components and gwt mvp to handle them. smartgwt is modelled on using a datasource which i would like to ideally extend (and populate using dto's (or proxy objects using gwt's request factory ) ) . however i have not got the hang of all these right now.

a) In the gwt mvp that google has layed out what exactly is the state of a place ? do we always send a person to a new place ? If not and the history maintains the place token then how is the state loaded ?

b) from another post about gwt mvp where is the model ? most of us tuned to typical mvc design paradigms would suppose that the model state is present within the presenter. i suppose then as suggested elsewhere the clientfactory would be the appropriate place to have the current model being displayed in the view stored ?

c) i would like to know if it is possible to attempt to use requestfactory to populate smartgwt databounded components ? ( from what i understand using the smartgwt server side framework does essentially the same thing .. transmitting only changes in the object graph across the wire ?)

d) On page 47 of David chandler's slide i dont quite understand the layout that is being proposed. ( 2 placeChangeHandler's ? 2 sets of widgetList's for each of the activity manager's ? Can someone kindly explain that ?

e) can anyone share their experience with gwt-sl (for server side spring integration ?)

thanks in advance to all the gwt gurus

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

喜爱皱眉﹌ 2024-11-12 07:59:08

从 SmartGWT 快速入门指南开始。我们强烈建议不要将 MVP 与 SmartGWT 一起使用,因为 SmartGWT 已经具有内置的数据绑定范例,我们相信它可以用更少的代码提供更多功能。

因此,深入学习 SmartGWT 数据绑定方法,浏览示例,尝试使用它,然后返回到您一直在查看的令人困惑的材料并问自己一个问题:它们是否简化了任何事情?它们是否可以更轻松地添加我需要的功能?如果没有,就不要理会他们。

Start with the SmartGWT QuickStart Guide. We strongly recommend against using MVP with SmartGWT, as SmartGWT already has a built-in data binding paradigm which we believe provides more features with far less code.

So, learn the SmartGWT data binding approach in depth, look through the samples, try using it, then return to the confusing materials you have been reviewing and ask yourself the question: do they simplify anything? Do they make it easier to add a feature I need? If not, don't bother with them.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文