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.

Bug 41742 - UI Responsiveness should be improved for VCS actions which open windows
Summary: UI Responsiveness should be improved for VCS actions which open windows
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscore (show other bugs)
Version: 4.x
Hardware: PC All
: P3 blocker (vote)
Assignee: issues@obsolete
Depends on: 35736
  Show dependency tree
Reported: 2004-04-06 15:05 UTC by Antonin Nebuzelsky
Modified: 2008-08-18 08:38 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Antonin Nebuzelsky 2004-04-06 15:05:13 UTC
Certain VCS actions, which retrieve information
from a VCS server and display it in a new window
(a new tab) in the editor area of the IDE, are not
responsive enough to the user.

Actions like CVS Log, CVS Status, CVS Annotate,
Graphical Diff and others only change the text in
the Status Line to "Command FOO is running..." and
then only after the command finishes the window is
created with the retrieved information.

The command execution can take up to tens of
seconds if the connection to the server is slow.
And in the worst case the text in the Status Line
can be in the meantime overwritten with some other

A better indication of the action being in
progress should be provided. Ideally the target
window should open ASAP (before 1 sec), the
progress of the command indicated in the window
and the window populated with the information as
the command completes.
Comment 1 Martin Entlicher 2004-04-06 15:18:39 UTC
This will affect UI, a UI spec is necessary.
Comment 2 Martin Entlicher 2004-04-07 13:21:18 UTC
Scheduling for future. This needs a UI redesign of existing
components, or some global progress indicator.
Comment 3 Martin Entlicher 2004-05-20 16:36:37 UTC
Decreasing priority to P3, to implement this we would have to change
many dialogs to present some "please wait" text until the command is
finished. In the case of diff, the solution would be very hard, since
we use public API to present the differences.

It would be best to wait till a generic progress indication is created
(issue #35736).
Comment 4 _ ttran 2004-05-21 14:30:31 UTC
Martin, it's not clear what is the reason to decrease the priority. 
IMHO the priority of the bug should be set based on the impact on the
user not on how hard the fix is
Comment 5 Martin Entlicher 2004-05-21 16:25:19 UTC
Right. But we can hardly fix this into promotion D and the best
approach would be to wait for the generic progress indication IMHO.
I do not think that this have a big impact on users, there were no
complaints on this from the community and we have this behavior in
many past releases.
Comment 6 Antonin Nebuzelsky 2004-05-21 17:11:53 UTC
Trungu, I agreed with Martin that this is perhaps downgradeable to P3
because there *is* some kind of indication that VCS action is running
(the text in the status bar, and more detailed indication under
Runtime/VCS) and the action is not blocking UI. We can discuss this on
our next meeting.
Comment 7 Peter Pis 2008-08-18 08:38:17 UTC
"vcscore" is no longer used. IMHO we can close this issue.