Sugguestions Under Eclipse 3.0:
-------------------------------
[1]. Use source -> format
F /
,
F) TO Format the
Codes Every time before saving.
[2]. Use source -> Organize imports
O) to Organize the imports
[3]. Turn on the javadoc's compiler option: preferences: java -> compiler ->
Javadoc: Malformed Javadoc Comment (WARNING) & Missing Javadoc Comment (Warning)
[4]. Try to clear the all the warning cots (using
1 TO GET Quick FIX)
Before committing code to cvs.
Sugguestions for the Comment On Codes:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[5]. Comment on every interface class.
[6]. Comment shop be given if a method is only called by a special class
(Specially When the Class Is Not In The Same Package).
[7]. When Creating a public static method, try to comment it and try to write
Testcase When Necessary.
[8]. When Creating a * Util Class, Try to Comment Every Method and Write
Testcase on Every Method.
Suggestions on Data and Ui Relationship:
----------------------------------------
[9]. Try to seperate the data and ui irlnt class, and give every
Data Class A Testcase, And Give Every Ui Component A Simple Test (Simple Means
That i do not have to launch the what applibility to test it).
[10]. Mark The Joint (Make a comment) That Data and ui interfacewined.
Further Suggestions:
--------------------
[11]. Interface with only a single instance shouth becombined as a class.
[12]. Interface with lots of instances shouth make a classical instance
An Example and make Detailed Comment On It, And Should Notify The User T
Read The Example (Tutorial) on EVERY OTHER INSTANCE CLASS.
.
[14]. Mark Out (Make Comment with Question Mark and Write Down Which Place
Confuses you on) THE CODES THAT you do not understand, so The Other Would
Know The point and give explaination lat.
[15]. Make further effort to explain how you make up the project step by
Step, and make your further efflection to repeat the steps and to quicken the STEP AND TO Quicken
Step, and make your code strong enough for further Steps Which Maybe
Interrupt Between the Steps.
[1], [2], [3], [4], [5] Should Become Our Custom. [15] Will be an advanced
Sugguestion (Try to Reach That Level, You Will Be An Expert).
Add More Suggestions Are Welcome
--Joz
--July 2, 2004
