Bug 2608 - Activation model between editors and views is problematic. (1GGZB5J)
Summary: Activation model between editors and views is problematic. (1GGZB5J)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows All
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin Haaland CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2001-10-10 22:39 EDT by Greg Adams CLA
Modified: 2002-04-17 14:17 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Adams CLA 2001-10-10 22:39:47 EDT
2.  Activation model between editors and views is problematic.
   (Not sure of PR #) We have many editors that have supporting views.
   Page Designer is a great example of this.  The "web" perspective has
   Thumbnail, Gallery, and Color Palette views that are used very closely
   with the PageDesigner Editor.  When these views are activated, the
   PageDesigner gets deactivated and all of its toolbar contributions are
   removed.  Since Page Designer has 3 rows of toolbar icons when its
   toolbar gets deactivated all of the views in the perspective re-layout.
   This makes it almost impossible to use the color palette and very
   difficult to use the Thumbnail view.  To really appreciate the severity
   of this problem, you have to see it.

NOTES:
GDA (7/16/01 6:54:00 PM)
	Deferred to 2.0 - WSAD advised
Comment 1 DJ Houghton CLA 2001-10-29 19:04:18 EST
PRODUCT VERSION:
0.9

 

Comment 2 Kevin Haaland CLA 2002-04-17 14:17:02 EDT
The activation model has been changed to address this request. 

In 1.0, when the user switched from an editor to a view (e.g. Outline) the 
Toolbar contributions were still visible but deactivated, the editor 
contributions were removed and the global actions targeted the active part. 

In 2.0, when the user swithces from an editor to a view (e.g. Outline) all 
contributions are preserved and target the active part. If the active part 
provides an implementation for these actions, they may be enabled. This will 
enable the Outline view better integration with the editor and still preseve 
the "actions target the active part" semantics. If the active part does not 
provide an implementation for an action it is disabled.