 |
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Maxim Shafirov - 12 Aug 08 19:52
Sounds undoubtedly great but will you tolerate absence of Goto Class/Goto File feature, for instance? To be more precise, what features you're expecting to work right from the start, until all the background indexing is done?
I am not the reporter, but I would expect to be able to work in a second project which I had already opened previously.
Well, I agree with Bas: the opening of one project should not block the other project. But for me, it would already be great if I could just browse the project using the project browser.
I can imagine that a later feature would be to do Goto Class/Goto File, but I could certainly life without it. It will be loaded anyhow, and I don't care that for the first minute, I have to browse by hand. But I do care that if I quickly want to show some code to a collegue, I'd rather use textpad or anything else quick, cause I don't want to risk a project load of more than a minute (and sometimes it's (a lot) more than a minute!). Btw, I'd certainly expect things like Goto Symbo, syntax highlighting, spring/java navigation, etc to work, cause I can imagine that you need a lot of parsing to get that to work. This is a great idea. Here is what I would like to be able to do (in order):
1) edit files (even if there is no syntax checking). This is before #2 because I should be able to immediately edit any files that I had open from the previous session This would allow me to immediately start working. My guess is that I would usually not hit #3 before that information is available. If I do, just queue it up behind the processes necessary for compile and let it fire off when ready. Maybe give me some sort of feedback so that I know why there is a delay. The more I think about this, the more I believe that this is a "killer feature". If the back-end can be modified for this, even more indexing, etc could be done to enable speed-ups later in the editor session, without the initial delay. +1. This is a great ticket! I can't think of a case when I'd need to look up a class using Goto Class... as soon as I open a project. What I need instantly is to see the project structure and the last opened files. Syntax checking and Spring XML validation, code navigation, Spring config/code namvigation would be the next immediate priority.
+1
I agree. Load the IDE If the project or JDK is loading in the background then obviously things aren't going to work fully so there should be a big visual indication of this |
||||||||||||||||||||||||||||||||||||
 |
|
Usability Problem
Open
Make loading of project a background task