Bug 58900 - [FastViews] Allow for tear-off to be global.
Summary: [FastViews] Allow for tear-off to be global.
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 59022
Blocks:
  Show dependency tree
 
Reported: 2004-04-16 14:24 EDT by Marcus Malcom CLA
Modified: 2019-09-06 16:08 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 Marcus Malcom CLA 2004-04-16 14:24:47 EDT
3.0 m8

1. allow for the concept of a "global" tear off
2. allow torn off views to be placed in a separate window

Currently if one tears off a view it applies to the current perspective only. It
would be nice if when a view is torn off, this could apply globally. In
addition, if this view could be placed in another window that would be very handy. 

This request is really in the context of the console view; however, the
application of it could be beneficial to other views. The console is targeted
because the console view will pop-up in other perspectives when it isn't really
desired. This happens when a process is running in the background and a user
switches perspectives to do other activities. The classic example is viewing DB
tables w/ a db viewer plug-in. The console becomes active and it would be nice
to have this global tear off capability so the user can do other things while
the console is fat dumb and happy in a tear off (instead of constantly getting
in the way).

Thanks!
Comment 1 Stefan Xenos CLA 2004-04-18 23:46:16 EDT
It might be possible to implement this without fixing bug 59022, but I suspect
that addressing the other issue first will simplify things. 
Comment 2 Eric Moffatt CLA 2007-06-20 10:59:40 EDT
This should be covered in a more general way...
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:08:49 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.