Bug 249538 - [WorkbenchLauncher] [API] consider making an API around WorkspaceChooserDialog
Summary: [WorkbenchLauncher] [API] consider making an API around WorkspaceChooserDialog
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.5   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-02 15:42 EDT by Chris Aniszczyk CLA
Modified: 2019-09-06 16:19 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Aniszczyk CLA 2008-10-02 15:42:45 EDT
I have run into quite a few people interested in using bits and pieces of the workspace chooser dialog.

The basic use case is that people want to hide the notion of workspaces but still reuse the lock checking and all that good. For example, imagine a usecase where someone was using workspaces as a way to partition working on large datasets based on geography.

An interesting question is also where this code would live. It's currently in org.eclipse.ui.ide and not awesome for people who are building "RCP" applications w/o the IDE bit.
Comment 1 Kim Horne CLA 2008-10-20 10:29:59 EDT
I've had thoughts to do this myself during my recent incursions into this codespace although I'm not entirely sure what the partioning would look like.  Any ideas?
Comment 2 Susan McCourt CLA 2009-07-15 12:38:21 EDT
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Comment 3 Boris Bokowski CLA 2009-11-26 16:32:34 EST
Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:19:18 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.