-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove animations from progress toolbar control #141
Remove animations from progress toolbar control #141
Conversation
30ab5ae
to
f315610
Compare
@jukzi any concerns? |
Why are animations bad? |
Would you mind to share a video/screenshot which animation is affected and why you want to remove it? |
@jukzi I think it is the small icon on the lower right when there is a running job but not sure... |
Animations are not bad per se. Not well written and tested animations are not helping the UI though esp. considering that underlying OSes already "animate" the widget . |
During startup StandardTrim creates an instance of Before this change TaskBarProgressManager supports animation, which This commit removes the animation logic but keeps the update logic of |
please attach the stacktraces. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't see a reason to remove the animation. but if we would remove it the drawing does not need to be rescheduled
|
||
if (isAnimated && taskItem != null && !taskItem.isDisposed()) { | ||
if (taskItem != null && !taskItem.isDisposed()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if it is not animated it does not need to be rescheduled
During startup StandardTrim creates an instance of TaskBarProgressManager in line 52. Before this change TaskBarProgressManager supports animation, which seems useless / overkill for progress reporting. This animation code also causes exception if you execute unit tests, as I discovered during a test run of the resource test suite. This commit removes the animation logic but keeps the update logic of updating the progress state of the item. I personal cannot note any difference in the resulting runtime Eclipse.
f315610
to
1bd6871
Compare
Done |
As the visual representation is the same I plan to merge this request soon. |
updateImage(null); | ||
} | ||
setProgressState(SWT.DEFAULT); | ||
updateImage(null); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the purpose of the job now? If it does always same, what's the point to schedule it at all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Who uses it amd wher / for what reason it is scheduled now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without the job you would not get an moving progress bar.
I think that the difference is that you now always have an "INDETERMINATE" progressbar but never showing actual progress (even though as @jukzi mentioned sometime wrong progress). |
As people seem not have the time to test (everyone seems to guess how it looks like), I merged, you can compare in the next I-build and see if something criticial is missing now. |
@vogella The commit does not work as intended: The code was NOT about the wrong progress report image - that is still there. Instead it removed the little overlay icon inside the System status bar indicating the image of the currently running job - for example during manual clean build: => i ask to revert since https://bugs.eclipse.org/bugs/show_bug.cgi?id=471310 claims it was important for them. Since you removed the code for unnamed exceptions please submit the Stacktrace instead and i can look into it. |
Also the change removed the working(!) Progress in the task bar. |
Have a look at the progress bar during any egit operation and be amazed. Unfortunately most projects don't call ProgressService.registerIconForFamily(...), even if they define job families. |
No description provided.