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.
This will affect UI, a UI spec is necessary.
Scheduling for future. This needs a UI redesign of existing
components, or some global progress indicator.
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
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
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.
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.
"vcscore" is no longer used. IMHO we can close this issue.