[gwt-contrib] Re: UiBinder and Model View Presenter

2009-08-20 Thread Amir Kashani
Brett, We did code splitting across the four major sections of our applications. Assume we have section A-D, each with their own mediator. We then have an ApplicationMediator, which is responsible for loading / unloading the four major sections and sticking them into the viewport. When

[gwt-contrib] Re: UiBinder and Model View Presenter

2009-08-19 Thread brett.wooldridge
Amir, After your post, I have been investigating PureMVC a bit. Since you used it, I have a question. In PureMVC, in the typical ApplicationFacade class there is an initializeController() override which registers all the commands. How does this fit with code- splitting? Currently our

[gwt-contrib] Re: UiBinder and Model View Presenter

2009-08-14 Thread Andrés Testi
Amir: Your answer is very interesting and detailed. Thank you very much for taking your time to answer my question. I will take a look in PureMVC. One of my big concerns is the translation of JSR 303 validations to client side. Regards. - Andrés On 13 ago, 18:36, Amir Kashani

[gwt-contrib] Re: UiBinder and Model View Presenter

2009-08-13 Thread Joel Webber
I don't want to speak for Ray here, since he gave the presentation, but my view is that they're largely orthogonal. UiBinder makes it easier to create views, but it has nothing in particular to say about how those views get bound to data. Its main goal is to remove the pain of UI construction, and

[gwt-contrib] Re: UiBinder and Model View Presenter

2009-08-13 Thread Amir Kashani
For my last work project, we used Kiyaa!, a GWT library that offers its own declarative UI system (and data-binding). In addition, we used PureMVC as a very lightweight MVC-framework. If you're familiar with PureMVC, you'll know that it's much closer to MVP, as described by Ray Ryan, than it is a