Agreed. Whether the reparsing is done automatically in the background or manually when the developer opens a file this feature would still be very useful. I trust JetBrains amazing staff to choose the easiest/simplest/most valuable to implement . I would be happy both way.
Jacques "Guillaume Laforge" <[EMAIL PROTECTED]> wrote in message aie2jq$t76$[EMAIL PROTECTED]">news:aie2jq$t76$[EMAIL PROTECTED]... > Even if we don't have any incremental compiler, it could still be possible > to parse all files in the background with a very little priority. Or when > the user hasn't issued any key stroke or mouse move. > It would be an option, of course, everybody doesn't want this feature to be > active :o) > > Guillaume > > > "Jacques Morel" <[EMAIL PROTECTED]> a �crit dans le message news: > aidufk$n2i$[EMAIL PROTECTED] > > +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 > > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
