+1 However I would only should problems not the absence of problems: For example VAJ & Eclipse put in any iconic/title view of a file that has errors a red X next to it to signify that it has problems. Of course they do incremental compile on save so it is very easy to maintain this info uptodate for them. However I think it is a powerful metaphor. In these IDEs you could do impact analysis or navigate quickly to errors with that because even the packages would show a red X if they contains a package or a file with a red X. I would still want to have these kind of feedback on my overall project even after a manually triggered compile and even if it might get stale. Each time the developer will follow the red X/square trail and open a file with an X IDEA could reparse and potential remove the red X/square if it doesn't need it.
Jacques "Willis Boyce" <[EMAIL PROTECTED]> wrote in message aid8kc$q4$[EMAIL PROTECTED]">news:aid8kc$q4$[EMAIL PROTECTED]... > It would be nice if the little square that glows green, yellow, or red > depending on the state of the source was also displayed next to each file in > the project tree. It shouldn't be obnoxious, just visible. > > Obviously I know that displaying the square next to every file would require > that every file be parsed, which might take a long time. So have a clear > square that means "not parsed yet." You don't even have to have a thread > parsing the files in the background; just display squares for files that > have been visited in the current editing session. Even this would be > useful, as I frequently move from file to file, leaving behind errors that I > need to fix. Seeing a little red square next to the files that I've left > with errors would help me keep track of what I still need to fix. > > Thanks, > Willis > > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
