将GWT MVP模式转换为Vaadin [英] Translating GWT MVP Pattern to Vaadin

问题描述

经过几个月的基于GWT开发应用程序，使用MVP模式+ Hibernate，我已经到了一个地步，应用程序的每一个小小的变化都是痛苦的，而且这些小部件看起来很差。
$ b

我也评估过Vaadin，它看起来非常有前途。数据绑定让我忘记DTO转换的方式看起来很有趣，但最终的结果看起来非常专业，所以我几乎相信要重做与Vaadin的合作。

关键是，我非常喜欢GWT中MVP的代码清洁，但是我一直无法找到合理的解释，说明如何将它适用于Vaadin，而不会丢掉大部分已完成的工作。 p>

我对代码适应的主要担忧是如何在Vaadin中使用GWT类，历史记录和事件总线。

有没有人经历了这个过程之后，才能向我们展示方式？或者，在Vaadin工作时可能有理由不惹恼MVP，现在我无法预见？

解决方案

感谢Jonas的回答。我检查过Vaadin的Navigator，但看起来beta beta
最后我决定不坚持使用GWT MVP，并遵循Vaadin中提供的模式之一。

最复杂的是将登录过程从GWT-mvp移动到Vaadin，但借助 wiki 指南并没有如此强悍。

我在一周内完成了这项工作，我感到非常欣慰不必处理复杂的DTO转换和RPC调用。

After several months developing an application based on GWT, using MVP pattern + Hibernate, I've come to a point where every small change in the application is a pain, and the widgets look very poor.

I've also evaluated Vaadin, and it looks very promising. The way that databinding allows me to forget DTO conversion, seems interesting, but also the final result looks very professional, so I'm almost convinced to redo the work with Vaadin.

The point, is that I like very much the code cleanness of MVP in GWT, but I haven't been able to find a reasonable explanation of how to adapt it to Vaadin, without throwing away most of the work already done.

My main concerns for code adaptation is how to use GWT classes, History and Eventbus, with Vaadin.

Has anybody gone through this process before that can show us the way?, or, maybe there are reasons to not mess with MVP when working with Vaadin, that I can't foresee by now?

解决方案

Thanks for the answer Jonas. I've checked Navigator for Vaadin, but looks beta Finally I decided not to stick to GWT MVP, and follow one of the patterns provided in Vaadin.

The most complex was to move the login procedure from GWT-mvp to Vaadin, but with the help of the wiki guide has not been so tough.

I've done it in a week, and I feel a great relief to do not have to deal with complex DTO conversion and RPC calls.

这篇关于将GWT MVP模式转换为Vaadin的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！