I want to point something out that I have seen crop up as a misperception quite a bit (here and at my work). Everyone seems to think IDEA is a better product because it's light on features. IDEA is very feature rich. The developers at IntelliJ have just put more time into interface issues than others have. A feature added in IDEA might be completely passive. It might be available from the keyboard and the mouse, from several locations. The interface won't yell at you when there is a problem with the new feature. In JBuilder, however, there might be a very similar feature. They would pick the simplest solution to code, and the safest solution to market: a wizard.
IDEA isn't much lighter than other editors. It just seems that way because the features aren't listed on 2-ton pull down menus. We shouldn't discourage IntelliJ from adding new features. Features are good. We should discourage them from getting lazy (I haven't seen it yet, but I'm watching). ----- Original Message ----- From: "Mike Cannon-Brookes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, December 06, 2001 9:57 PM Subject: Re: [Eap-features] Re: EJB wizard > This is exactly what XDoclet does - and it works perfectly with IDEA, > and free. > > http://www.sf.net/projects/xdoclet (just a happy user here - no > affiliation) > > I'm 100% behind whoever was talking about lots of smaller tools to do > specific jobs, that makes coding much easier. > > Heaven forbid the day that IDEA becomes like JBloater. > > -mike > On Fri, 2001-12-07 at 08:34, Ingi Gauti Ragnarsson wrote: > > I can hear that you are not that happy with my suggestion, I'm not a > > wizard guy, the application I used before IntelliJ was TextPad, and I > > still use it for lot's of other editing other than Java files. > > > > But do you realize how quicker you would be programming CMP beans, if > > the Entity bean, ejb-jar.xml file and helper classes would all be > > connected. Change one variable, and it would change all the files. Also > > all the debugging trouble you get sometimes with EJB beans. Like if a > > method in the remote interface isn't the same as in the as in the EJB > > bean, you get an error and lot's of other things. I have no doubt that > > if you have developed a EJB bean you know that everything has to be > > perfect. > > > > Well that's my thought. > > Ingi > > > > > > _______________________________________________ > > Eap-features mailing list > > [EMAIL PROTECTED] > > http://www.intellij.com/mailman/listinfo/eap-features > -- > Cheers, > Mike > > -- > Mike Cannon-Brookes :: [EMAIL PROTECTED] > > Atlassian :: http://www.atlassian.com > Supporting YOUR J2EE World > > > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-features > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
