Bug 229840 - [Presentations] Give more control over the workbench look to custom Presentation
Summary: [Presentations] Give more control over the workbench look to custom Presentation
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement with 5 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-01 14:33 EDT by L. Mihalkovic CLA
Modified: 2019-09-06 16:14 EDT (History)
1 user (show)

See Also:


Attachments
Example presentation using this functionality (97.03 KB, image/gif)
2008-05-01 14:35 EDT, L. Mihalkovic CLA
no flags Details
A possible implementation (8.66 KB, patch)
2008-05-01 14:40 EDT, L. Mihalkovic CLA
no flags Details | Diff
Possible implementation (9.14 KB, patch)
2008-05-01 14:55 EDT, L. Mihalkovic CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description L. Mihalkovic CLA 2008-05-01 14:33:21 EDT
A couple days ago, a change was made to org.eclipse.ui.presentations.AbstractPresentationFactory to allow presentations to control the Sash used between the various part stacks.

In order to provide more control to presentation designers, I think it would advantageous to do the same with the size of the trim spacing used around the entire central area of a window. I have actually made a similar change to my own workbench to be able to  create a more Mac like presentation.
Comment 1 L. Mihalkovic CLA 2008-05-01 14:35:28 EDT
Created attachment 98348 [details]
Example presentation using this functionality
Comment 2 L. Mihalkovic CLA 2008-05-01 14:40:45 EDT
Created attachment 98349 [details]
A possible implementation
Comment 3 L. Mihalkovic CLA 2008-05-01 14:55:48 EDT
Created attachment 98353 [details]
Possible implementation

 - Added convenience constructor
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:14:42 EDT
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.