This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
Hi Guys, I am still having problems seeing the benefit of have a MVC pattern in the GUI! With web components like Servlets and JSP it makes prefect sense! What I understand is that you have one class with all the GUI components and "Hook methods - as Mark explains". Another class which is your controller. And a third class which is your model. Say for example you decide to extends AbstractTableModel in your model class, that directly links your Model to Swing. Which of these 3 components will you be able to reuses? The only way I can see reusability is if you want a different GUI, with different layout. Can anyone explain this to me please? One last question is whether the View may call methods on the model? Kind Regards Fred
Controller knows about GUI and Model but View should not know anything about the Controller or Model. Also, your table model is not necessarily the same as app model. As to what other benefits does this offer- a clean separation of functionality and encapsulation of low level connecting, locking etc. Any other ideas?
Aruna A. Raghavan<br />SCJP, SCJD, SCWCD
Joined: Jun 11, 2002
Hi Aruna, Can the GUI calls methods on the Table model class?
Joined: May 14, 2002
Hi Fred, In my code, view sets up the model initally. But once the controller is called to fetch search results, it updates the model and view gets a tableUpdated event. This is how I've done it. Aruna.