Sugguestions under Eclipse 3.0 and others

原创 2004年07月02日 17:30:00
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 codes (using +1 to get quick fix)
before committing codes to CVS.

Sugguestions for the comment on codes:
[5]. Comment on every Interface class.
[6]. Comment should 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
a JUnit 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 into different 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 whole application to test it).
[10]. Mark the joint (make a comment) that DATA and UI interwined.

Further suggestions:
[11]. Interface with only a single instance should be combined as a Class.
[12]. Interface with lots of instances should make a classical instance
an example and make detailed comment on it, and should notify the user to
read the example(tutorial) on every other instance Class.
[13]. If some classes' logic fit some classical model, try to comment out
such model, and give a URI for the reader to get a further reading.
[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 later.
[15]. Make further effort to explain how you make up the project step by
step, and make your further effort to repeat the steps and to quicken the
step, and make your codes 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).


--July 2, 2004

Eclipse and others

    Eclipse,今天有段时间是放在它身上的。PP的界面,简单的操作,至少对我而言够用的功能。玩玩还是很爽。    据说,先用它的可视化工具建立SWT,然后再修改代码是件不错的工作。     但...
  • flykobesummer
  • flykobesummer
  • 2008年11月20日 09:33
  • 395

存储过程中的when others then 和 raise 何意义?

 EXCEPTION when others then rollback; dbms_output.put_line('code:' || sqlcode); dbm...
  • luman1991
  • luman1991
  • 2017年02月21日 21:22
  • 435


1、打开Eclipse4.2,新建一个Maven项目     1)选择maven的archetype为maven-archetype-webapp     2)填写项目信息     2...
  • lizhibin3944
  • lizhibin3944
  • 2014年01月17日 15:53
  • 1164


转载:自戎马一生 译文:全面提速 英文:
  • alibert
  • alibert
  • 2016年05月25日 11:12
  • 726

在oracle中要谨慎使用when others then

在oracle中一般不要使用when others then,否则会掩盖软件的错误提示。 如果只是判断查不到数据时的处理,应该用when no_datafound then 待续......
  • sxdtzhp
  • sxdtzhp
  • 2013年06月27日 10:03
  • 1367

SVN:is already under version control 错误 解决方案(已解决)

SVN:is already under version control 错误 解决方案(已解决)
  • zhangjq520
  • zhangjq520
  • 2017年09月12日 14:31
  • 501


  • chinaCsdnV2
  • chinaCsdnV2
  • 2017年02月23日 21:56
  • 4804


建立项目使用Eclipse建一个File –> New –> OtherNext ,Next,选择maven-archetype-webapp输入坐标信息,Finish稍等片刻,我们的webapp骨架...
  • frankcheng5143
  • frankcheng5143
  • 2016年05月03日 17:46
  • 9796

.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filena

解决方法 : sudo  chmod g-wx,o-wx /home/refresh/.python-eggs
  • livefun
  • livefun
  • 2013年12月11日 15:16
  • 1467

UserWarning: .python-eggs is writable by group/others and vulnerable to attack when used with get_r

chmod g+rwx,o+rwx ~/Python-eggs/ chmod g-w,o-w ~/Python-eggs/ ll ~/.python-eggs total 12 d...
  • northeastsqure
  • northeastsqure
  • 2016年11月04日 09:36
  • 881
您举报文章:Sugguestions under Eclipse 3.0 and others