Java Class Architecture for swing GUI programming -
I am writing an application that requires a large amount of swing GUI components. I have a lot of difficulty in organizing classes: Is systematic and systematic layout a method of class architecture?
In addition, I have many anonymous and internal classes and my main square has become bloated. However, when I put internal class event handlers in different files, I am having trouble reaching the components of my main category. Is there a method to organize large swingયુwag applications internally?
In the big swing projects, I become part of the app such as:
- < Li>
-
Use a different package for each screen, especially if you have to apply customized table fields or other complex data structures
-
Do not use anonymous and internal sections, rather than an action listener and check ActionEvent.getActionCommand () there.
A GPI element, such as JPNL, JDILOG etc.
Comments
Post a Comment