This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The classpath rescan progress indication dialog says Checking changes of: x Package: x |=================........| and it may take tens of seconds or even minutes for some projects to finish. The users are frequently wondering why checking of changes takes sooo long. They don't realize that the process mainly deserializes persistent information and this takes majority of the time. To better set the expectations, the dialog should rather say something like Checking changes and reading persistent data of: x Package: x |=================........|
Dusan, please evaluate.
I got your point, however I think, that this detailed description isn't necessary and by the way dialog could became too wide...
Thanks Dusan. Based on the feedback of our UI engineer I am closing this as WONTFIX.
I saw many users ask why the checking of changes takes so long when checking of file timestamps is very fast operation... Even Jesse Glick asked this question. I think it is a good indication that the current text is confusing for the users. I don't insist on "Checking changes and reading persistent data of:" but something similarly descriptive should be used.
Reassigning to Dusan for further evaluation.
For example a fresh feedback from a user on nbusers: --- %< --- My main issue here is the same unresolved one: NB 4 insists on synchronously checking the time stamps on all classes and jars in compilation, etc, paths of all open project prior to letting me do any work. --- >% --- We should improve performance of the rescanning task (there are separate issues about this) but the users should also be told that this is not only simple checking of timestamps.
Rudolfe, please evaluate. Thanks
Progress dialog is implemented according to UI spec. http://ui.netbeans.org/docs/hi/javamdr/refactoring_design.html Changing to enhancement for future releases.
OK, changing the summary. Take this as a bug in UI Spec and correct it. Are HIE folks paying attention to issues at all? Will this trivial change require review of 10 people before anyone does anything with this?
Implementing the "longer" version of this dialog text will not improve the synoptical value. Checking changes of: x Package: x |=================........| The sense of this way designed progress dialog is obvious enough. Information, that IDE reading some persistent data will not increase the satisfaction of the user in this case. The important information is, that IDE does some checking and this takes time. Sure, sometimes it can take few minutes. Maybe a detailed description could be provided by the documentation, but this is a really negligible issue.
RESOLVED FIXED state is supposed to be used for issues which are, surprisingly, fixed. I guess you want to change to WONTFIX... OK, I don't care anymore. I will point the tens of users who are confused to this issue.
We cannot do anything with this issue. It is implemented according to ui spec. And ui spec was verified by 2 UI engineers (Dusan and Rudolf). They confirm, that this dialog is correct. Correct resolution is INVALID IMO. If you don't agree feel free to change resolution to WONTFIX or whatever, but don't leave this issue in opened state.
I'm not quite convinced by rbock's evaluation either. As user I usually feel better if I see what the UI is really doing than clueless looking at frozen progressbar for minutes. Why this issue cannot be changed to ENHANCEMENT, it is valid enhancement IMO. After we collect more VOC we can change our opinion and create better UI.
Reorganization of java component