N`s Java ;-)

星期六, 八月 07, 2004

java资源

JAVA开发工具+环境


1.tomcat URL
http://cvs.apache.org/builds/jakarta-tomcat-5/nightly/jakarta-tomcat-5-bin-20040510.tar.gz

2.jCreate

Jcreator 3.00 pro (092) 下载地址: http://www.findown.com/down.asp?id=15158&no=5

注册码:

JCreator Pro v3.00.094(092)
Username: P145460-Brian Luke
Key: 00HE3T-MX6F41-7E9CFN-68745A-RD1PAJ-0GKKPP-YYJVDR-CXJXHG-6GFXX8


3.mysql 数据库 与 mm驱动
数据库安装程序:http://202.99.219.235/soft/598.html
驱动 http://www.mysql.com/products/connector/j/

4. intellij idea javaIDE工具
(1) intellijidea 3.0
下载地址:http://www.88oo.com/list.asp?id=2744
注册码:javaone/79350-V9TMH-VR8X3-GMARI-IQ4HU-EW8J5
这个注册码很好使,对于Linux上的IntelliJ IDEA3.0同样适用
(2)v4.0
下载地址: http://www.fixdown.com/soft/6496.asp?soft=down
注册机:URL http://key.fixdown.com/key.asp?id=2004-4-13 13:40:31c3988&key=keydown

JAVA电子书

Thinking in Java 3rd Edition 中文版 http://www.wgqqh.com/shhgs/tij.html

JCREATOR3.0 中文乱码的一种解决办法

JCREATOR3.0 中文乱码的一种解决办法

引起汉字显示不正常的地方主要有: 注释(包括/**/ //) 字符串("") 解决方案:
打开: \Xinox Software\JCreatorV3\Syntax\java.syn 或者 jsp.syn(写jsp也会有乱码)等,找到以下内容,其中将注释(/**/ //)和字符串的开始和结尾字符去掉:

<%
%>
/* 去掉/*
*/ 去掉*/


// 去掉//

" 去掉"
" 去掉"
'
'

-+*/<>!~%^&|=
[](){}
\


最后显示成:(将注释符号去掉)

<%
%>








'
'

-+*/<>!~%^&|=
[](){}
\

---------------------------------------------------
在处理jsp,和java.syn一样处理
关于你可以删除
<!--
-->
这里面的<!--,-->

星期一, 八月 02, 2004

Sugguestions under Eclipse 3.0 and others

http://blog.csdn.net/reve/archive/2004/07/02/32578.aspx

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 writea 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 everyDATA class a TestCase, and give every UI component a simple test(Simple meansthat 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 instancean example and make detailed comment on it, and should notify the user toread the example(tutorial) on every other instance Class.
[13]. If some classes' logic fit some classical model, try to comment outsuch 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 wouldknow 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 thestep, 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 advancedsugguestion(Try to reach that level, you will be an expert).
ADDING MORE SUGGESTIONS ARE WELCOME--Joz--July 2, 2004
posted on 2004年07月02日 5:30 PM