Hi Gregor, I think I need to clarify something.
We didn't follow MVC dogma blindly! Based on experience on working on large scale projects we know that there is no other good option available to develop and "maintain" enterprise level applications. I know that not following well established patterns might seem easier at first but in a long run the price that you would pay for the maintenance gonna be much higher. Honestly, suggesting MVC patterns is more like sharing experience than a religious war. And finally, I don't have anything against ModelDelegate, but I think you wouldn't use it in a jsp web site by putting all controllers code inside jsp. (which is possible and most newbies start coding this way) You definitely use a well established MVC framework. My point is know that we have other lightweight frameworks that claim they provide full MVC support we should consider them more seriously. Kind regards, Reza. On Feb 24, 10:55 pm, gregor <[email protected]> wrote: > Hi Charles, > > > - do I have to duplicate datas in my Model (MVC) ? > > - what about asyncCallback when calling a service: whe doing that part > > in a widget (view side), I was able to display a window (Window.alert) > > when the RPC failed. Now, this code is done in the Model (MVC) so it > > doesn't make sense to add this kind of code there... > > - how can I handle exceptions? For example, as I can't display a > > window in the Model part, I would like throw an exception which will > > be thrown from the Model to the View through the controller.. How can > > I do that? I can see that onFailure method from AsyncCallback doesn't > > throw any controlled exception. In addition, it is an asynchronous > > call... > > You observations illustrate some reasons why when Swing and SWT where > designed they did not follow classic MVC, but implemented a variant of > it sometimes called Model Delegate. It's more convenient and concise. > There are no downsides because there is nothing to stop you > implementing full blown MVC (by which I mean rigorous separation of > view and controller in the UI) if you need to. See: > > http://c2.com/cgi/wiki?ModelDelegate > > GWT is loosely based on Swing/SWT programming model (as far as it can > given it runs as javascript). It makes sense to follow the programming > model of your tool kit, or at least to investigate why it follows the > pattern it does, rather than blindly follow traditional MVC dogma. > > regards > gregor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
