I am using a Command pattern to seperate my user interface from my business logic. I will have quite a few dialog screens that will be triggered from the main frame. These Dialogs will in turn interact with the business layer and may need to be able to update the parent frame. I was considering just extending the Command pattern out another iteration and having the dialog classes conform to it. Anyone have any better ideas or foresee any problems with that? Thank you for you help.
Could you elaborate a little more? From what I can remember about the Command pattern, it is used to implement some sort of undoable Action or Transaction. I've never heard it used to separate business and UI logic. For UI-business logic separation, the Model-View-Controller (MVC) pattern comes to mind. Allen Holub (http://www.holub.com) also discusses an alternative to MVC (which he says is fundamentally flawed) in his articles about a "Visual-Proxy" pattern. Junilu
The best ideas are the crazy ones. If you have a crazy idea and it works, it's really valuable.—Kent Beck