我比较喜欢看技术方面的文章，每次都是看RSS的时候将链接拖到MyIE，然后统一来看，有时候机房要关门了也没看完，我就从任务管理器里将MyIE的进程关掉，这样下次打开MyIE时选择打开上次关闭的网页就可以继续看了。
在我的快速启动栏上有三个记事本的快捷方式，一个连到文档中的Problem.txt，用于记录一些要完成的任务、程序中需要新增的功能。都是什么时候想到就什么时候记上去，比较方便。第二个连到Task.txt，用于记录要看的一些技术或要试用的软件，都是在看技术文章时记下来的。
使用FreeTextEditor预览Blog
使用http://xmlbuddy.com/ XmlBuddy Plugin
看Eclipse的VS.net皮肤http://www.sf.net/projects/eclipse-skins
看developworks上的Opensource中“SWT&JFace系列”
RCP（eclipse.org/rcp） RIA看收藏
开发一个远程桌面辅助程序。
将ImageAnalyser改为standalone
Wink(Screencast)在安装程序
用我的本本发的第一篇Blog哦，爽就一个字，呵呵
The Eclipse 3.1 has a new feature. Now the Java project settings like Compiler and Code Style can be shared with the entire team using the version control tool.
To do this right click the project in Package Explorer or Navigator view and got to either Java Code Style or Java Compiler options. Check the Enable project specific settings.
This will create a .settings folder in the project root. Eclipse will add and maintain the project specific configuration in this folder. Commit this folder to the version control. Thats it. Now the project settings are shared with the team. When the other team members synchronize with the repository they will get the project settings too. Any team member can update and check in the settings. Cool!
都在这几个文件夹里：
org.eclipse.debug.ui/icons
org.eclipse.pde.ui/icons
org.eclipse.jdt.ui/icons
org.eclipse.vcm.ui/icons
org.eclipse.team.ui/icons
org.eclipse.ant.ui/icons
org.eclipse.help.ui/icons
org.eclipse.ui/icons
org.eclipse.ui.views/icons
org.eclipse.ui.console/icons
一个比较全的Icon网页：
http://www.codehaus.org/~bwalding/eclipse-icons/以后找Eclipse的图片就方便了，: )
The wizard in this code is a standard wizard that displays pages, then generates code in the doFinish method. What is most interesting about this class is that in performFinish, it demonstrates how to interact with Eclipse's process monitor for tasks that take a long time.
/**//**
* This method is called when 'Finish' button is pressed
* in the wizard. We will create an operation and run it
* using wizard as execution context.
*/
public boolean performFinish() 
{
final String containerName = page.getContainerName();
final String fileName = page.getFileName();
IRunnableWithProgress op = new IRunnableWithProgress()
{
public void run(IProgressMonitor monitor)
throws InvocationTargetException
{
try {
doFinish(containerName, fileName, monitor);
} catch (CoreException e) {
throw new InvocationTargetException(e);
} finally {
monitor.done();
}
}
};
try {
getContainer().run(true, false, op);
} catch (InterruptedException e) {
return false;
} catch (InvocationTargetException e) {
Throwable realException = e.getTargetException();
MessageDialog.openError(
getShell(),
"Error", realException.getMessage());
return false;
}
return true;
}
/**//* */
/**//**
* The worker method. It will find the container, create
* the file if missing or just replace its contents, and
* open the editor on the newly created file.
*/
private void doFinish(
String containerName,
String fileName,
IProgressMonitor monitor)
throws CoreException
{
// create a sample file
monitor.beginTask("Creating " + fileName, 2);
IWorkspaceRoot root =
ResourcesPlugin.getWorkspace().getRoot();
IResource resource = root.findMember(
new Path(containerName));
if (!resource.exists() ||
!(resource instanceof IContainer))
{
throwCoreException("Container \"" +
containerName + "\" does not exist.");
}
IContainer container = (IContainer) resource;
final IFile file =
container.getFile(new Path(fileName));
try {
InputStream stream = openContentStream();
if (file.exists()) {
file.setContents(stream, true, true, monitor);
} else {
file.create(stream, true, monitor);
}
stream.close();
} catch (IOException e) {
}
monitor.worked(1);
monitor.setTaskName("Opening file for editing");
getShell().getDisplay().asyncExec(new Runnable() {
public void run() {
IWorkbenchPage page =
PlatformUI.getWorkbench().
getActiveWorkbenchWindow().getActivePage();
try {
IDE.openEditor(page, file, true);
} catch (PartInitException e) {
}
}
});
monitor.worked(1);
}
This code is a simple SWT wizard page. The most interesting characteristic of this class is in the handleBrowse method. This method uses Eclipse's ContainerSelectionDialog for displaying the folders in the workspace.
/**
* Uses the standard container selection dialog to
* choose the new value for the container field.
*/
private void handleBrowse() {
ContainerSelectionDialog dialog =
new ContainerSelectionDialog(
getShell(),
ResourcesPlugin.getWorkspace().getRoot(),
false,
"Select new file container");
if (dialog.open() == ContainerSelectionDialog.OK) {
Object[] result = dialog.getResult();
if (result.length == 1) {
containerText.setText(
((Path)result[0]).toOSString());
}
}
}
Posted by: Michael Yuan on June 27, 2005 @ 07:55 PM
The JBoss TrailBlazer is a collection of interactive demos, runnable sample applications, technical articles, and other materials to help developers learn a new technology. These are part of JBoss's latest effort to make enterprise Java more easily accessible to everyone.
There are currently two EJB 3.0 related TrailBlazer applications. They are hosted on the latest JBoss AS 4.0.3 RC1, which comes with full EJB 3.0 support out-of-the-box, and is available for generic public over the Internet.
- The JBoss EJB 3.0 TrailBlazer focuses on the EJB 3.0 POJO programming model. It has 20 technical articles, more than a dozen live sample applications (with online source code), and several flash demonstrations. It covers almost all aspects of EJB 3.0 programming. Notable "trails" include:
- The JBoss IDE TrailBlazer has a series of flash demonstrations to show you how to develop, deploy, and debug a JBoss EJB 3.0 application from scratch using the IDE.
在Eclipse的插件体系中，所有的类库文件都是以插件的形式存在的。如果你的Plugin项目要用到第三方API库或者另一个工程的API，你可以将他们包装成一个插件，这就是库插件的含义。
在我们小组的设计中，Plugin和控制逻辑是分成两个工程单独开发的，Plugin主要实现界面功能，通过调用控制逻辑实现数据存储、Blog发布、打印等功能，所以接触到了制作库插件这个过程，现在写下来，希望有点帮助。
如何制作库插件：
将库工程转换为Plugin工程，在MANIFEST.MF的overview里定义ID，在Runtime里加入你要公开的包（Exported Packages）。OK
如何使用库插件，主要分为三步：
1、在Dependencies Tab的Required Plug-ins中加入你的库插件（保证输出项目时导出相应的库插件）
2、然后Compute build path（使项目能够顺利通过编译）
3、在运行对话框的Plugin Tab里单击Add required plugins，这样项目才能正常运行
有一点忘了就会挺郁闷的！
RCP Eclipse Plugin
详细的制作Help过程我就不说了，在这里可以找到。
要注意三个问题：
1、添加的插件要齐全，使用Help要增加以下几个插件：
org.apache.ant
org.apache.lucene
org.eclipse.help.appserver
org.eclipse.help.base
org.eclipse.help.ui
org.eclipse.help.webapp
org.eclipse.tomcat
2、在Build里添加html文件的信息，使html文件能正确导出，如：
bin.includes = plugin.xml,\
*.jar,\
plugin.properties,\
book.xml,\
html/,\
icons/
3、在html文件中不能有中文的链接（显示为乱码，服务器会提示找不到该文件），所以html和图片的名称尽量用英文，内容用中文倒没有问题。
In some small companies, we may encounter such problems: Having some excellent ideas or innovation, but have no time to implement due to the afraid of disorder existing plans. It's a bad impact for innovation.
Some guys have developed a method: Hackathon. With this method, feedburner group add 7 useful functions to their feed reader software in 1 day.
Now let's have a look at the Hackathon method: (too simple)
在每周一段规定的时间内（Feedburner小组用了一天），小组成员各自开发与项目内容无关的功能，自己认为好的想法都可以实现（最好是那种在几个小时内就可以完成的功能），然后把做好的功能完好地集成到项目中。
some english, some chinese, enjoy it. : )
links about Hackathon:
http://blog.jot.com/archives/2005/05/09/jotspot-inagural-hackathon
A good website for us eclipsors. Enjoy it!
http://eclipse.techforge.com/index.php
想知道在JavaOne 2005上，哪些书最畅销吗？ 这是J1上的图书销售商给出的Top 10:
其中有2本JBoss的书，3本Spring的书和1本Hibernate的。你是否需要补充一下你的书架了？
Thank you for your recent evaluation of ReportMill.
A few questions:
Did you have a chance to install and test the product?
Are there any product features in ReportMill that you would like or found missing?
Are you using an existing reporting tool?
Do you plan on embedding reporting in an existing or new application?
Does it make sense to schedule a demo to give you a quick overview of the features?
Regards,
Brian Noll
ReportMill Operations
brian@reportmill.com
1-(609)-678-0058
“Reporting for Java Developers”
Our tutorial is here :
http://reportmill.com/support/docs/tutorial.pdf
Our design documentation is here:
http://reportmill.com/support/docs/user_guide.pdf
Our developer documentation is here:
http://reportmill.com/rm8/support/DevDocs.html
Our video based training is here:
http://reportmill.com/support/videos/animation
Our Yahoo community is here:
http://groups.yahoo.com/group/reportmill/join
被Baggio抢了个先，555
真忙啊，又要搞课程设计，又要准备后天的Computer Architect考试。两边都不能放松，还希望两边都做得好。确是一件难事，有时看到同学还有时间玩游戏，而自己编程编的头都大了，感觉是应该放松一下，自己其实没必要那么忙的。时时想起远方一位好友的话：大学除了学知识，还要学会怎么玩。可能正常的应该是这样的，而我可能走了比较顺畅的路，现在都没法改回来了。
越来越“理解”《小薇》里的一句台词：聪明是他最大的缺点，帅是他天生的缺陷。呵呵
1. Learn to say, “I don’t know.” If used when
appropriate, it will be often.
2. It is easier to get into something than it is to get out
of it.
3. If you are not criticized, you may not be doing much.
4. Look for what is missing. Many know how to
improve what’s there, but few can see what isn’t
there.
5. Viewgraph rule: When something appears on a viewgraph
(an overhead transparency), assume the world
knows about it, and deal with it accordingly.
6. Work for a boss with whom you are comfortable
telling it like it is. Remember that you can’t pick
your relatives, but you can pick your boss.
7. Constantly review developments to make sure that
the actual benefits are what they are supposed to
be. Avoid Newton’s Law.
8. However menial and trivial your early assignments
may appear, give them your best efforts.
9. Persistence or tenacity is the disposition to persevere
in spite of difficulties, discouragement, or indifference.
Don’t be known as a good starter but a
poor finisher.
10. In completing a project, don’t wait for others; go
after them, and make sure it gets done.
11. Confirm your instructions and the commitments of
others in writing. Don’t assume it will get done!
12. Don’t be timid; speak up. Express yourself, and
promote your ideas.
13. Practice shows that those who speak the most
knowingly and confidently often end up with the
assignment to get it done.
14. Strive for brevity and clarity in oral and written
reports.
15. Be extremely careful of the accuracy of your
statements.
16. Don’t overlook the fact that you are working for a
boss.
• Keep him or her informed. Avoid surprises!
• Whatever the boss wants takes top priority.
17. Promises, schedules, and estimates are important
instruments in a well-ordered business.
• You must make promises. Don’t lean on the
often-used phrase, “I can’t estimate it because it
depends upon many uncertain factors.”
18. Never direct a complaint to the top. A serious
offense is to “cc” a person’s boss.
19. When dealing with outsiders, remember that you
represent the company. Be careful of your
commitments.
20. Cultivate the habit of “boiling matters down” to the
simplest terms. An elevator speech is the best way.
21. Don’t get excited in engineering emergencies. Keep
your feet on the ground.
22. Cultivate the habit of making quick, clean-cut
decisions.
23. When making decisions, the pros are much easier to
deal with than the cons.Your boss wants to see
the cons also.
24. Don’t ever lose your sense of humor.
25. Have fun at what you do. It will reflect in your work.
No one likes a grump except another grump.
It's a bug fix version.
The last release candidate version.
After weeks, Eclipse3.1 Release will be able to download.
我们在写Plugin程序时，涉及的类一般都比较多（可能来自各个插件），有时候只知道类的名字，但不知道类所在的包名，查文档又有点浪费时间。
但假如我们能够记住该类的一个方法或字段的话，我们就可以在类名后输入".方法名"或".字段"，然后按Ctrl+1，或右键选择Quick Fix，Eclipse就会提供一个import列表，从中选择正确的包名就可以了。
RCP学习笔记（RCP Tutorial）
在一个RCP中，我们将org.eclipse.core.runtime.applications扩展（extension）定义为工程中主程序的id，将org.eclipse.ui.perspectives扩展定义为工程中Perspective的id。
RCP的最小Plugin集合为org.eclipse.core.runtime、org.eclipse.ui，所以我们肯定要将他们加到Dependencies Tab
Plugin.xml用到的变量（如：%pluginName）在build.properties里定义，可以通过它实现国际化
plugin.xml的大体结构：
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.1"?>
<plugin
id="org.eclipse.ui.tutorials.rcp.part1"
name
version
provider-name
<runtime>
<library name="yourproject.jar">
<export name="*">
</library>
</runtime>
<requires>
<import plugin="org.eclipse.core.runtime"/>
<import plugin="org.eclipse.ui"/>
</requires>
<extension
id="RCPApplication"
point="org.eclipse.core.runtime.applications">
<application>
<run
class="your application path">
</run>
</application>
</extension>
<extension
point="org.eclipse.ui.perspectives">
<perspective
name="Display Name"
class=
id="eclipse.ui.tutorials.rcp.part1.RCPPerspective">
</perspective>
</extension>
</plugin>
由于历史原因，eclipse优先考虑plugin的id而不是最顶层元素（如extension）的，所以尽管plugin.xml声明extension的id为RCPApplication，但这个extension的id还是org.eclipse.ui.tutorials.rcp.part1.RcpApplication。而perspective的id写在了perspective这个子元素里（不是顶层id），所以他的id要写成org.eclipse.ui.tutorials.rcp.part1.RCPPerspective，而不能像RCPApplication extension的id那样缩写。
Main program：
主程序入口由org.eclipse.core.runtime.applications extension指定，告诉Eclipse runtime生成一个它的实例。Main program要实现IPlatformRunnable接口，程序执行代码放在run()里。
一个Perspective（视角：由视图、编辑器、导航器组成）
至少要定义一个Perspective，实现IPerspectiveFactory，并将它赋值给org.eclipse.ui.perspectives extension。这个接口最主要的方法是createInitialLayout(),他负责管理程序start时views和editor的放置方式等。
Workbench Advisor管理Workbench上的toolbar、perspectives等的添加和删除（主要方法：getInitialWindowPerspectiveId()返回默认Perspective的id）
文章最后提到怎么部署一个独立的RCP程序，步骤比较烦，3.1M7以上版本可以参考PainFree RCP
Problem Description：新建了一个RCP Mail的Template Example，运行正常，但是当我将在另一个RCP工程里建好的View放进来时，工程运行就抛出Invalid Menu Extension (Path is invalid): org.eclipse.ui.edit.text.gotoLastEditPosition，而且菜单和工具栏里多出了一些Eclipse自己的东西（如Search，Go to Last Edit Location）。捣动半天未果，后来偶然发现另外一个一模一样的运行配置运行OK，只是使用了另一个Workspace，比较一下发现，出错工程的Workspace多了三四个Plugin的配置（org.eclipse.core.resources，org.eclipse.core.runtime，org.eclipse.debug.core，org.eclipse.debug.ui），而成功的工程workspace只有org.eclipse.ui.workbench的Plugin配置，其他都一样，即使我复制过来也不好使。现在只能用以前的那个成功的配置了，好使，但不知道为什么会出现上述情况，
难道是成功的工程已经将一些Extension注册了，所以后面的工程都用不了。
可能的原因：今天看Eclipse的RCP Tutorial时注意到Eclipse RCP所需的Plugin最小集是org.eclipse.core.runtime和org.eclipse.ui，又记起昨天使用了PDE的调试功能，所以org.eclipse.debug.core，org.eclipse.debug.ui可能是调试时生成的，或者是以前别的项目用过出错工程的workspace目录，生成了一些别的Plugin目录，而多出的Plugin在Plugin.xml文件里注册的menu在我的程序里没有被添加（或者没有定义对应的MenuPath），于是就抛出了：Invalid Menu Extension (Path is invalid)
不过还有一个问题：怎么workspace的.Plugin文件夹里只有org.eclipse.ui.workbench而没有org.eclipse.core.runtime，有谁知道这是为什么吗？