I totally agree that IntelliJ should seriously look at higher level functionalities like a "code smell" detector or an "OO coach". These are the logical next steps after refactoring support that further exploit IDEA's superb code analysis capabilites and bring great value to developers.
So, +100 from me, with one condition: don't add too much new functionality without having properly finished existing functionality (like refactoring support). Also, even though I agree that such mundane and boring things as the sort order of lists should not be IntelliJ's highest priority, they should not be neglected either. In other words, please grow IDEA at a "healthy", not too fast pace. IntelliJ, you have a great product, but keep an eye on the competition (they're catching up). My $0.03 -Thomas > -----Original Message----- > From: Alain RAVET [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 29, 2001 11:19 PM > To: [EMAIL PROTECTED] > Subject: RE: [Eap-features] Automatically create compiler output path > > > Manuel Laflamme wrote > >> It would be great that IDEA creates the compiler output > path if it does not already exist. > > > In fact, this is part of the bigger "project > templates/w$z$rd" request. > > This is quite frustrating to have to build each new project > from scratch. > I won't pronounce the forbidden word "W*ZARD", but there is a > place for something new here. > Without going as far as JBuilder - though I wouldn't oppose > to it -, IDEA could be smarter when it comes to project creation. > > Why does it offer to create 'src', but not 'classes', or 'javadoc'. > I would also add 'data' and 'test'. > I have created a zipped skeleton for Tomcat based projects, > that I unzip on the IDEA created structure when I need it. > Based on your type of project (EJB, applet, standalone), you > would use the same trick with another base. > > > We cross a lot of fine-tuning/polishing type of requests in > this list, and I have posted my share of it. > But I feel we should also talk about bigger changes. > > For example, I made 2 - unsuccessful - attempts to suggest > some form of code analysis, or "code smell" detector. > When do you refactor? When you detected a "code smell" > (duplicate, poorly named member, classes with 150 methods...) > BTW, Oracle JDeveloper, and XPtools (will) offer it. > I feel this is the time now to start introducing this kind of > functionalities. > > Is nobody interested in higher level improvements? > Is this list doomed to be the > "Ctrl-Alt-Tab-Space" should sort the list in > alphabetical order, and not .. > request list? > > > > Alain Ravet > > > This mail has been checked by exiscan. > To be safe, please scan the mail attachements with your local > virus scanner ! > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-features > ************************************ If this email is not intended for you, or you are not responsible for the delivery of this message to the addressee, please note that this message may contain ITT Privileged/Proprietary Information. In such a case, you may not copy or deliver this message to anyone. You should destroy this message and kindly notify the sender by reply email. Information contained in this message that does not relate to the business of ITT is neither endorsed by nor attributable to ITT. ************************************ _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
