Questions about "Best Practices" in using Swing as UI layer
Hello everyone. I'm trying to create an architecture that is targeted to ease the efforts on developing Swing applications. I have a 3 year background on Web-Based applications, and about 1 year and half using JavaServer Faces.
The first thing I've noticed was that is not so trivial promoting a certain level of reuse in Swing. I'm trying to do something that I do in JSF - a BaseActionMessageHandler, that has methods to throw i18n messages to a customizable panel or to a JOptionPane, a BaseDataModelAction, that provides population utilities to DataModels, and a BaseFrameAction, that is injected with an entity, a service interface and has methods to execute operations on the service layer.
I want to use inheritance to provide template-like functionality to UIs, something like have a JFrame with all panels aligned correctly, and just adding (or injecting via IoC) the needed components in the frames.
I'm thinking on designing an utility base class to ease the notification of components about business layer events too.
Is this the correct approach? If not, can you experts show me the right path?
Thanks in advance
Rafael Mauricio Nami