Community
Participate
Working Groups
In order to reflect things happening in an editor that does not have the focus, it could be good to have the capability of changing some characteristics of the title bar (ie: put the title in bold, italic, change the color of the title bar, etc.) The same API is needed for the views as well. Note to nick: check if the IProgressService works the same way for editors and views (hint: you were pretty sure it was :-)
We have API already to change the title tab (I assume that is what you mean) in the PartPane showBusy() and showHighlight(). You can implement these how you like. What else do you need?
PartPane is not API. It leaves in org.eclipse.ui.internal.
The idea here is to open up the kind of bolding/italicizing of the titlebar that the workbench currently does internally for jobs. It should be possible for views themselves to indicate "busy" and "done" states, in addition to "something new to check out" (perhaps the same as "done"), whether or not it uses jobs. The example is a new message arriving in an instant messaging view.
The progress support would be changed to be layered on top of this public API.
[since this API isn't Mac specific setting Hardware & OS to All]
W.r.t tab italicizing, the IWorkbenchSiteProgressService works for views but does not work for editors. This is probably because the default implementation of PartPane#setBusy(boolean) does nothing. Only ViewPane has an implementation of this method that does anything.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Remy is now responsible for watching the [ViewMgmt] category.
(In reply to comment #6) > W.r.t tab italicizing, the IWorkbenchSiteProgressService works for views but > does not work for editors. This is probably because the default implementation > of PartPane#setBusy(boolean) does nothing. Only ViewPane has an implementation > of this method that does anything. That would be bug 86221. Pascal, would you be fine with me marking this as a duplicate of that?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
