I'm having a major usability problem in IDEA 6.0 rather compared to IDEA 5.0. Any suggestions are welcomed!
Consider a typical web project, with the file structure like:
project/WEB-INF/src/(100+ more classes)
project/(100+ more jsp files)
Working on the project is usually divided into:
a) working with servlet sources (business logic and data model tier)
b) working with JSP templates (presentation tier)
In IDEA 5.0, I've been using "Project" and "Packages" tabs to switch between these contexts. "Projects" showed all the JSPs and "Packages" showed the packages heirarchy tree. Both tabs had separate tree controls with their own expand/collapse states handled and saved independently, which was very useful. Working with "Packages" tabs didn't affect "Projects" tab, and vice versa.
In IDEA 6.0, there's no more any tabs, since they were replaced with "View as:" combobox.
The irritating thing with the combobox is that the corresponding trees become affected by each other. The worst use-case is as follows:
1. Switch to Projects view
2. Navigate to some directory which corresponds to the domain you're working with, like "admin/blocks"
3. Switch to Packages view
4. Navigate and select a deeply lying class like com.company.project.common.model.Entity
5. Switch back to Projects.
Huh! The carefully-selected tree position in Projects view is lost. The view is instead cluttered with project/WEB-INF/src/com/company/project/common/model tree structure, which is completely useless (I use dedicated "Packages" view to browse classes, thanks).
Am I missing something? Should I use another approach for developing web applications?
(I won't even mention that the new combobox control is less usable then tabs per se, requiring "point-click-point again-click again" logic to make a simple switch instead of trivial point-and-click when using tabs. I've always appreciated IDEA's outstanding usability, so the whole issue is quite strange for me.)