In the upcoming Maia EAP you will find a slightly different Commit Changes dialog.
IntelliJ IDEA 8.1 brings you many new and improved Flex support features:
We have also created a live demo that shows the advanced IntelliJ IDEA Flex support features in action: smart Flex code completion, Flex code analysis with quick-fixes, Flex refactoring, convenient project navigation and usage search. You can watch it now or download archive for offline viewing.
Raise your hats to Ted for his recent IntelliJ IDEA Tips series! Ted sheds light on the wallflower features of IntelliJ IDEA, as well as new ways of using well-known features and the most beneficial plug-ins.
Stay tuned for new enlightening blogposts from Ted!
Another valuable contribution comes from Cedric Champeau, who has shown how structural search in IntelliJ IDEA can help you find try/catch performance bottlenecks.
If you are looking for ways to speed up IntelliJ IDEA on your computer, some of these
And, last but not least – 9 more reasons to love your IDEA of choice 
– thanks to Messi.
Yesterday the Utah Java User Group held its regular monthly meeting, and to shake things up a bit, they decided to make it an IDE Shootout between some popular IDEs: Eclipse, IntelliJ IDEA, NetBeans, and BEA Workshop. During the meeting, the audience was polled to find out which IDE they were currently using, and about 75 people raised their hands for Eclipse, while only 10 for IDEA, and another 10 split between the other 2. At the end of the presentations, the audience was asked to vote on two awards for the IDEs. The first was called the “Second Look Award” and reflected the idea that after spending years and years getting used to one IDE, it can be challenging to move to a new tool. The UJUG site described it like this:
The UJUG ‘IDE Second Look Award’ signifies the impact of both the presentation and the abilities of the IDE presented. Switching to a new IDE is difficult. Typically, a Software Engineer has used the same IDE for many years, slowly becoming a master of it. To even consider looking at a different IDE is the willingness to take a step into the unknown. The Salt Lake City, Utah Java User’s Group shows its appreciation to the presenter for preparing and creating an influential presentation and to the developers of the IDE, convincing the largest number of people to take the first step of considering a new IDE.
Winner: IntelliJ - Etienne Studer
The second award was the:
UJUG IDE People’s Choice Award
The UJUG ‘IDE People’s Choice Award’ signifies the impact of both the presentation and the abilities of the IDE presented. The Salt Lake City, Utah Java User’s Group shows its appreciation to the presenter for preparing and creating an influential presentation and to the developers of the IDE which impressed the largest number of UJUG attendees.Winner: IntelliJ - Etienne Studer
We would like to thank Etienne for his expertise and the great presentation that helped IntelliJ IDEA win these significant awards.
There are many development tools in the world. For now, picking the right one that suits for anyone’s requirements is a complicated task. It’s not about the number of supported frameworks, servers or languages. It’s not even about the number of different features implemented in this or that tool. Picking the right tool is about how good it’s made. How all the features are glued together and integrated one with another, and what’s even more important - that you have to feel this tool is made for you. That is, how good you and the tool are getting along and how it lets you be more productive and effective.
You can read the agile developer blog post that also discusses whether a tool is worth the money it costs. By the way, the example he gives at the end of his article is really, really impressive.
Furthermore, the No Fluff Just Stuff Antology author, Neal Ford speaks about how effective IntelliJ IDEA is in his non-stop talking about IntelliJ. He also mentions that people who use IntelliJ IDEA are way more passionate about using their product and are always happy to share their experience.
Sebastiano Pilla wrote a very interesting article about his experiences with the top four IDEs. After testing each one according to his criteria, his pick was IntelliJ IDEA:
“IDEA simply worked without getting in my way with arbitrary limitations. Where it shines is in the editor, the configurability and the speed at which everything operates: in a “shopping list” of features it might lose to the others, but it wins because the implementation and the design feel more consistent to me.”
The lesson is clear. Comparing IDEs by simple feature lists won’t necessarily find you the best IDE. You need to actually try it to be sure it will be right for you. Look for an IDE that boosts your productivity by doing what you expect it to do without getting in the way, i.e. it ‘just works’. A feature list might tell you a feature is there, but it won’t tell you how well it works.
Two interesting polls include IntelliJ IDEA and TeamCity among the tools surveyed for John Ferguson Smart’s upcoming book, Java Power Tools.
In the poll for code quality, IntelliJ IDEA currently has the highest rating, likely due to its powerful and easy-to-use static code analysis features, including over 600 code inspections, built-in code coverage analysis, and dependency analysis.
TeamCity was only recently added to the continuous integration poll, so it’s a bit low on votes at the moment. Originally, the poll had only open source tools, but Smart added some commercial offerings because of the rapidly changing landscape of the continuous integration server market, which I talked about in a recent idea.log post. TeamCity represents a new generation of CI servers due to its attention to the problems of broken-build syndrome, when a broken build causes the whole team’s productivity to drop. TeamCity tackles broken-build syndrome and much more. Are you already doing test-driven development and interested in increasing team productivity? You may want to check out TeamCity.
In the spirit of healthy dialogue, I’m looking for a whole series of reviews of IntelliJ IDEA 6.0. If you know of any reviews or comparisons involving IDEA 6.0, feel free to comment on this post, and include the links!
The good, the bad, and the ugly are all appreciated!
So to get the ball rolling, here’s a recent review from an Eclipse user, Unnsse Khan, who just spoke at the SDJUG in California!
Enjoy! http://trusoftware.blogspot.com/2006/11/eclipse-vs-intellij-idea.html
Technorati Tags: IntelliJ IntelliJ IDEA Eclipse NetBeans Review IntelliJ Review Eclipse Review NetBeans Review
It is always a pleasure to get a positive feedback on the products we develop, especially enterily new ones. We really appreciate the Continuous Integration Revisited post, where the author describes TeamCity’s features and his own experience. He noted that TeamCity’s installation and configuration was really quick and transparent, pointed at the benefits of the Delayed commit feature, and discussed possibility of creating the build configurations using different build runners and testing frameworks for remote code testing.
Now about new features that are not mentioned in this review, since they appeared only in the latest EAP build (that you can download at http://www.jetbrains.net/confluence/display/TW/Download). Among several enhancements and new features, the most important one is displaying of the Code Inspection results in a dedicated tab on Results page. Now you can locate the dead code, find probable bugs, check coding guidelines and specifications violations right on the web. TeamCity’s code inspections are based on the IntelliJ IDEA’s Static Code Analysis and Code Inspection tool, so you can use the power of more than 600 code inspections for remote code analysis.
Right now, you can’t navigate to the discovered problems from the web to IntelliJ IDEA. But this functionality will be implemented in the nearest IntelliJ IDEA EAP builds.
To get the full list of changes and new features in TeamCity EAPs, monitor the changes log.
IntelliJ IDEA is not “only Java” IDE. If you have a license, you don’t need a separate XML editor (as well as HTML/CSS or JavaScript ones). These editors come with IntelliJ IDEA “out-of-the-box”.
Here is a couple of links that may help you with being more productive with XML editing:
One more useful tip is that IntelliJ IDEA completes XML documents even if no schema is specified. All tag and attribute names and values are completed based on what you are typing. IntelliJ IDEA tracks your input and suggests new tag names and attributes for already used tags. It also filters out attributes that have already been specified for a tag, so you don’t have to worry about duplicates.
For example, you typed a tag like this:
When you are about to create another shopitem tag and start typing “price” attributes, you will get the completion:
Start typing another attribute, and IntelliJ IDEA will help you avoid duplicates by removing what you already typed from completion list.
Edit XML with pleasure!
Twitts about IntelliJ IDEA
