This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 55167 - [PresentationAPI] Need to add progress support to all presentations
Summary: [PresentationAPI] Need to add progress support to all presentations
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: 4.4 M7   Edit
Assignee: Paul Webster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-17 16:14 EST by Tod Creasey CLA
Modified: 2014-05-02 04:47 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tod Creasey CLA 2004-03-17 16:14:25 EST
From an email Nick sent...I have assigned to Stefan as he is currently working 
in this space - please let me know if you need anything from me.

PartTabFolderPresentation is only used for views.  Need to ensure that 
this works for editors too, in EditorPresentation too.
The font logic there now is different than for PartTabFolderPresentation.

We want to maintain the following invariants, for both views and editors:
- if any jobs running in the part, then font is italic
- else if any jobs were running, but have all completed, and part not yet 
activated, then font is bold
- else font is plain

I suggest having a common updateFont(IPresentablePart) method in 
PartTabFolderPresentation, calling this from the subclasses for the initial 
case and when the busy state changes.

This will require maintaining a separate latch for the "all jobs completed but 
part not yet activated" state, for each part.
Any logic that is independent of how the busy state is presented should be 
encapsulated in IPresentablePart.  That is, it should be easy to move to using 
colours rather than fonts to show the busy state without having to worry about 
the logic above.  I suggest changing IPresentablePart.isBusy() to be a 3-
valued int getBusyState() method (not busy, busy, and done), and maintaining 
the latch there.
Comment 1 Paul Webster CLA 2006-09-28 15:13:09 EDT
Is this still a problem in 3.3?

PW
Comment 2 Denis Roy CLA 2007-06-22 09:32:36 EDT
Changes requested on bug 193523
Comment 3 Lars Vogel CLA 2014-05-02 04:47:59 EDT
The PresentationAPI has been deprecated with the Eclipse 4.x release and it has been replaced with the CSS engine. I therefore close this bugs as WONTFIX. In case your bug report is still valid for the Eclipse 4.4 release, please open a new bug report for it.