Chinese

新手通常是从选择合适的开发工具开始了，这篇文章作者讲了自己的经历，个人感觉还是有些用了，因为我就认识许多使用并崇拜eclipse的人，但他们使用他写代码时候就是当文本编辑器一样了，我们需要的是提高工作效率，让自己有更多的自由支配时间的开发工具，并不只是开源。
A good JSP editor
2/5/05 12:53 PM
Java, Programming, ATG Dynamo
This is the story of how I found a good JSP editor.

Code completion is the killer feature for me. It's the reason I moved from Emacs to JBuilder, and from JBuilder to Eclipse. Code completion means less syntax to think about, and more attention to devote to code. So it came as a shock when I started putting JSP together and found out that 'ctrl-space' didn't do anything in Eclipse.

I had a list of specific features though:

Must support custom tag libraries.
Must complete tags and attributes of tags.
Must support embedded Java syntax.
Must complete methods and recognize Java classes inside <% %>.
Must validate Java expressions for syntax and missing variables.
Must not crash, hang or install crap onto IDE.

Not too complicated, right? I want a JSP editor and just a JSP editor. No autodeployed J2EE applications. No fancy GUI. No "debug on the fly" feature. In short, no crap.

My first try was Lomboz. It didn't say anything about tag completion. It wanted me to install EMT and SDO 2.1.0. There's no release build of SDO 2.1.0, so I had to use an integration build. This did not inspire confidence. I installed it. It didn't recognize my tags. This is because the JSP editor didn't recognize ATG 7.0 as a valid editor. There was no way to add a new application server, no way to add custom tag libraries to a project (rather than an app server). Finally, I using some embedded Java, and tried some code completion. It froze Eclipse for a couple of seconds before doing... nothing. I deleted it.

My second try was Sysdeo. People said nice things about this, but it was obviously Tomcat specific, and it said nothing about tag completion. I passed over it.

My third try was MyEclipse. I didn't have very high hopes from the website, but I installed it and played with the JSP editor. I remember that it sort of worked. Unfortunately, it also installed a ton of other plugins, none of which I really wanted. These plugins clogged Eclipse up with useless bells and whistles. I deleted it.

My fourth try was IBM Webtools. I'd heard about this piece of code through comments in passing, but I'd never actually seen anyone say they'd used it themselves. I tried to download the code and found it depended on several other libraries. I tried to install those libraries and found more dependencies. I tried with the libraries I had and crashed Eclipse several times. I reinstalled Eclipse and decided to try something else.

My fifth try was NitroX. After all the previous tools, I was burnt. I really didn't want to install another Eclipse plugin, and it showed in my reaction to the NitroX webpage. Big, slogan-heavy, and with massive images perfect for the under-5 set. I had a hard time finding out the JSP features in the editor. (Looking back now, the website has improved dramatically since the first time I saw it. There's a direct link to the feature list, and more text.) The JSP editor looked like it would do exactly what I wanted, even down to validating EL expressions. But the visual editor was not a turn on, it was an 80MB download, and I just couldn't face the idea of trying to get it to work and ending up with a ton of useless semi-working features that took up memory and CPU in my IDE. This was entirely my failing, and you can download the JSP editor free here and try it out yourself. (Although looking at the site now, it only works on 3.0, and I'm on 3.1. So much for that idea.)

The next day, I decided that my problem was Eclipse. I started looking at standalone JSP editors. Because I wanted deep understanding of Java, I really needed something that was IDE like... but not tied to my regular IDE. So I skipped over JSF Studio.

I tried IntelliJ IDEA and fell in love. It supported every feature I'd asked for, was around the same price as NitroX, and wasn't Eclipse. Setting up ATG Dynamo was simple and painfree, and it understood a JSP page was actually code and complained if I did something that would break a page compile. I decided to see what Hani was fapping about and bought the thing.

So far IDEA makes a perfect JSP editor. The only thing I can complain about is that it doesn't understand EL expressions, and even that is only a minor niggle. My experience using IDEA as an IDE is another story altogether, and will be told another time.

P.S. I know that I've probably missed some editors and given short shrift to others. In particular, I missed XMLSpy and Stylus Studio. These would probably make good solutions for front-end developers who don't care so much about the code.

原文见
http://tersesystems.com/post/5400060.jhtml