Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313775

Summary:	trim should have known separator slots
Product:	[Eclipse Project] e4	Reporter:	Susan McCourt <susan>
Component:	UI	Assignee:	Project Inbox <e4.ui-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:	Eric Moffatt <emoffatt>
Severity:	normal
Priority:	P3	CC:	emoffatt, gheorghe
Version:	1.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Susan McCourt

2010-05-20 13:08:25 EDT

Within a trim bar, it would be nice to be able to do things like force a trim contribution to a certain location.

A real-world example we have is wanting to right-justify the perspective switcher rather than have it simply flow into the trim bar.  

Eric and I discussed that one approach we could take for 1.0 would be to have "trim separators"...these things could grow to fill up empty space, which could force items to the right.  Kind of like menu slots.

Whatever we define for the SDK workbench wouldn't necessarily be the insertion model for other apps, but it'd be nice if the separator concept were generic enough that apps could define their own separators in any trim....

I'd be happy with one separator in each trim composite.
Something that split the area.
So the top and bottom trim could be effective divided into left and right, and the left and right trim could be divided into top and bottom.

Comment 1 Eric Moffatt

2010-06-21 11:26:19 EDT

We could do this for the compatibility's starting model I guess but wouldn't it be better for RCP apps to just place the 'spacer' into their model as they deem appropriate (including ids...) ? 

IMO the e4 RCP story should be 'you *own* your model, make it whatever shape you want'.

Comment 2 Eclipse Genie

2019-02-25 00:20:44 EST

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.

--
The automated Eclipse Genie.

Comment 3 Lars Vogel

2019-06-05 07:34:33 EDT

This is a mass change to close all e4 bugs marked with "stalebug" whiteboard.

If this bug is still valid, please reopen and remove the "stalebug" keyword.