Bug 55830 - [FastView] Not enough control over fast views from IPerspectiveFactory
Summary: [FastView] Not enough control over fast views from IPerspectiveFactory
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2004-03-24 00:58 EST by Justin Smith CLA
Modified: 2009-08-30 02:11 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 Justin Smith CLA 2004-03-24 00:58:29 EST
You can specify a view to be a fast view on the IPageLayout in a
IPerspectiveFactory but you have no more control than that. In the latest builds
the fast view bar is at the bottom of the window and when you click the fast
view icon then it shows a horizontally maximised fast view with the vertical
height being able to be set via the ratio (float value). I want it show like the
old fast views being vertically maximised but the horizontal size via the ratio.

The option to pin a fast view has also disappeared in the latest builds, where
is it!!! Once this feature makes it back in I also like to specify where the
fast view will get pinn'ed via the IPerspectiveFactory (i.e. to a Placeholder or
Folder).
Comment 1 Justin Smith CLA 2004-04-22 10:08:04 EDT
The level of control I want to acheive is to be able to add fastviews to the
PageLayout and then also specify the placeholder for them when the user does
perform a restore they go to the correct area. I also want to be able to say if
the fast view is Vertical or Horizontal.

Part of this bug could be because if you specify a place holder for a view then
the code for addFastView will not process because the view ref id already exists:
	public void addFastView(String id, float ratio) {
		if (checkPartInLayout(id))
			return;
.....

This will cause the fast view not to be added.

If you perform it the other way with the FastView being added first and then the
placeholder being added, it will ignore the placeholder information.
Comment 2 Stefan Xenos CLA 2004-04-23 18:20:00 EDT
The "pin" option is still available - just not from the toolbar. Right-clicki on
the fast view's tab and de-select "fast view". That will do the same thing as
the pin icon. You can also re-dock a fast view using drag and drop.

The default location of fast views has changed from M8. They will always appear
on the left now.

We have no plans to expose the "horizontal/vertical" fastview option as API
(since this concept might be removed in the future in favor of 2 resize sashes).
However, it is possible that there *might* be future API to specify the
preferred dimensions of a view (in pixels), which would also be used to
determine the view's initial orientation and size when used as a fastview.

The suggestion to permit placeholders for fastviews is good, but it is unlikely
if this enhancement will be added for 3.0.

Comment 3 Justin Smith CLA 2004-04-26 04:24:43 EDT
I have tested modifying the PageLayout class by making the checkPartInLayout(..)
method always return false and it worked by enabling you to specifiy a view in a
placeholder and then adding it as a fast view. I don't know what this will
potentially break but it is just a check method and maybe there could be someway
to override/configure.

This would only take a very small time to implement and gives a terrific
enhancement by allowing the fast view to be pin'ed to a specific view folder
rather than just the active one.

Please reconsider this minor change, otherwise we will need to include a
"hacked" version of workbench.jar from now on in our RCP application.
Comment 4 Eric Moffatt CLA 2006-06-23 16:06:25 EDT
Cleaning up defect lists by setting ones without recent traffic to 'REMIND'.
Comment 5 Denis Roy CLA 2009-08-30 02:11:21 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.