I'm a little new to the pattern idea but it seems like I have a situation where a pattern may help. I am beginning to build GUI screens for an application. It seems that I should be able to build the screens and centralize the event handling into one class. I would like to separate the GUI from the business logic as much as possible because I will not be involved in implementing the business logic. My idea is to have one central class that handles all of the GUI events and in turn knows what business logic (objects) to call in order to process the event. Finally, this event handler will update the GUI component. I think this is similar to the MVC architecture used for the swing components. I would think this concept has been played out before and is available in the form of a pattern that may prevent me from making stupid mistakes. Any input would be greatly appreciated. Thank you.
At the risk of sounding like a broken record in this forum, as an alternative to the MVC, check out what Allen Holub has to say about it and GUIs for OO systems. He talks about a Visual-Proxy pattern. It's kind of a combination of Facade, Proxy, and Abstract Factory. Takes a while to digest though and it may contradict things you have heard before. FWIW, I agree with the guy for the most part. Junilu
[This message has been edited by JUNILU LACAR (edited May 19, 2001).]
The best ideas are the crazy ones. If you have a crazy idea and it works, it's really valuable.—Kent Beck