Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 159708 - [FastViews] RCP: possibility to customize fast view
Summary: [FastViews] RCP: possibility to customize fast view
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Eric Moffatt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-04 07:48 EDT by Michael Seele CLA
Modified: 2007-06-21 10:09 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Seele CLA 2006-10-04 07:48:09 EDT 
please add a posibility to use the fast view toolbar/control in a application which overrides createWindowContents in WorkbenchWindowAdvisor!!!
Comment 1 Eric Moffatt CLA 2007-06-20 15:10:31 EDT 
We're deprecating the FVB so no work is anticipated here...

BTW, we're already looking at a better way to allow RCP clients to access our 'internal' layout code...
Comment 2 Michael Seele CLA 2007-06-21 01:37:01 EDT 
so is there a bug open for "better way to allow RCP clients to access our
'internal' layout code..."? can you post the bug #
Comment 3 Eric Moffatt CLA 2007-06-21 10:09:46 EDT 
No bug # per se. We're in design discussions around the current presentation code in general and being better at this is one of the design requriements...

We're aiming at a more Model/View approach that would allow us to much more amenable to replacement of discreet components. The 'model' would support some defined structure which would be 'rendered' by some WBW implementation. This would entail us opening up our various 'renders' (of which the TrimLayout would be one) so that RCP clients could choose between our default renderer for a particular model or they could replace the renderer at any level (i.e. you could leave the 'shell' renderer in place (controlling the 'trim' and the 'center') while replacing the renderer for the "TabStack'.

No guarantees here (we're still in the blue-sky brainstorming) but we understand that making this separation possible is -required- for any reasonable replacement for our current presentation story.