Actually, looking (briefly!) at Ian's links, GWT could probably be best described as ModelDelegate, which is classified as a derivative of MVC and is what Swing is called it seems.:
http://c2.com/cgi/wiki?ModelDelegate Also this is a short explanation from Wikipedia of MVC and Swing GUI frameworks [edit] Java: Java Swing Java Swing is different from the other frameworks in that it supports two MVC patterns: Model Frame level model—Like other frameworks, the design of the real model is usually left to the developer. Control level model—Swing also supports models on the level of controls (elements of the graphical user interface). Unlike other frameworks, Swing exposes the internal storage of each control as a model. View The view is represented by a class that inherits from Component. Controller Java Swing doesn't use a single controller. Because its event model is based on interfaces, it is common to create an anonymous action class for each event.[citation needed] In fact, the real controller is in a separate thread, the Event dispatching thread. It catches and propagates the events to the view and model. I think this explanation fits very well into GWT's model - we have the browser's event queue, and we also often use anonymous inner classes for event listeners. On Jan 30, 12:03 pm, gregor <[email protected]> wrote: > I think the guts of MVC was invented (as so much was) at Xerox's Palo > Alto research center when they invented the first WIMP UIs in the > 70's. This fed into Smalltalk and was taken up also with Apple Lisa by > the early 80's. Since most systems at the time were based around text > screens run from mainframes, they needed a new programming model that > could handle the idea of the user being able to click on any widget on > the screen in any order at any time rather than being run through a > predetermined script, hence MVC. > > I'm not sure they had the idea of the Observer pattern at the time, > and I think Ben is right that the Observer pattern is now an > alternative/replacement for Controllers in GUI programming. GWT is > designed to use it. In that sense, I would say maybe the best pattern > for GWT client coding might be called Model View Observer rather than > MVC. > > On Jan 29, 8:56 pm, Flemming Boller <[email protected]> wrote: > > > Now that you mention SmallTalk... I of course agree! > > when I wrote LISP, I have a funny feeling it about, but I thought it was so > > :-) > > > anyway that for the correction. > > /Flemming > > > On Thu, Jan 29, 2009 at 9:23 PM, Ian Petersen <[email protected]> wrote: > > > > On Thu, Jan 29, 2009 at 11:33 AM, Flemming Boller > > > <[email protected]> wrote: > > > > MVC goes long back in time. long before web frameworks. I think it came > > > from > > > > the language LISP. > > > > I don't know how relevant this is, but MVC was first so-named by a > > > bunch of people designing GUIs in SmallTalk. I don't remember the > > > timeframe, but it was definitely before web frameworks became at all > > > popular. There's some interesting discussion of the pattern here: > > >http://c2.com/cgi/wiki?ModelViewController Don't get too lost in that > > > site--it's easy to burn a lot of time wandering around the Portland > > > Pattern Repository's wiki. > > > > Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
