Hello All,
I am in the process of developing my first "real" app using SWT Designer from Instantiations for the UI layer.
I planned to use the ClientBilling example discussed the SWT Designer's docs as a model to follow in completing my first app, and I'm wondering if the ClientBilling example really represents a best practices approach.
A class diagram is here:
http://www.arkadia-systems.com/clientbilling/ClientBilling.jpg Individual source files are here:
http://www.arkadia-systems.com/clientbilling/ClientBillingUI.java http://www.arkadia-systems.com/clientbilling/ClientBillingProc.java Others are here also, just use the appropriate class name if interested.
Full source may be downloaded from:
http://www.cs.umanitoba.ca/~eclipse/ClientBilling.zip ClientBillingUI class has:
Fields: 54
Methods: 12
Lines of code per method min: 9, max 273, avg: 63
Lines of code: 1041
I get the idea from Fowler's Refactoring (sections on Long Method and Large Class) that this code may not be well designed from a best practices viewpoint.
I would really appreciate any comments from those more familiar than I with Today's best practices regarding this app. Specifically in terms of good/bad design and future maintainability.
Thanks, your comments are very much appreciated.
-Glen