Bug 116414 - [EFS][Dialogs] Need better file dialog for external EFS file systems
Summary: [EFS][Dialogs] Need better file dialog for external EFS file systems
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks: 113373 154126
  Show dependency tree
 
Reported: 2005-11-15 04:56 EST by Dirk Baeumer CLA
Modified: 2019-09-06 16:09 EDT (History)
10 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Baeumer CLA 2005-11-15 04:56:15 EST
Now that EFS is in place we need a way in the user interface to access non local
file systems.

To not have additional button for each file system on the various dialogs (as we
have now for external and workspace internal files) I propose that we have a
combined file selection dialog which allows to pick files and folders from:

- the workspace
- the local file system
- any external file system contributed via EFS
Comment 1 Douglas Pollock CLA 2005-11-15 09:07:59 EST
Duplicate of Bug 116327? 
Comment 2 John Arthorne CLA 2005-11-15 09:48:25 EST
Tod, I don't know if you want to consider this a duplicate of your existing bug
or a dependent bug that deals only with the file dialog issue.
Comment 3 Tod Creasey CLA 2006-04-07 16:00:43 EDT
The dialogs that can access EFS can do this using

FileSystemContributor#browseFileSystem(String initialPath, Shell shell)
Comment 4 Martin Aeschlimann CLA 2006-04-21 04:32:45 EDT
Tod, has there been any change to the new project wizard as described in comment 0?
If not, can you set the bug to later or wontfix?
Comment 5 Tod Creasey CLA 2006-04-21 09:27:30 EDT
Right - I see your point. Lets mark it REMIND as it is not such a bad idea - a lot of ourt wizards need revisting now.
Comment 6 Tod Creasey CLA 2006-04-21 09:28:04 EDT
Marking REMIND
Comment 7 Tod Creasey CLA 2006-10-11 10:45:40 EDT
reopening as this may be added as part of the extended file system support toime permitting
Comment 8 John Arthorne CLA 2006-11-17 12:58:09 EST
Tod, this is the other big EFS-related piece.  Lower priority than the import wizards though, I would say.
Comment 9 Chris Recoskie CLA 2008-07-25 12:30:27 EDT
I am currently running into this myself.  I need an EFS-capable browsing dialog that can be invoked from property pages and the like.

Right now using FileSystemContributer.browseFileSystem() is really clunky, because it invokes its own dialog.  So in my case, I'd have to go to my directory property in the property page, hit "Browse...", go to a dialog where I can select the filesystem I want to use, then hit another "Browse..." button to invoke the filesystem specific browse dialog.  Ugh.  And it's too much clutter if for every property I have to put the filesystem dropdown next to my browse button in order to eliminate the need for the first dialog.

So... what to do?  So far my best idea is that you would need to have a generic dialog which houses the filesystem dropdown, and then have each FilesystemContributer contribute a Composite for the rest of the UI that would appear below it in the dialog when that filesystem is selected in the dropdown.

Anyone else have an idea of how they think this should look?  Even this seems sort of hacky to me but I couldn't think of a better way that would still provide the required flexibility, because to my mind, we really have no idea what a given filesystem will need to present UI-wise.

I thought briefly about making a generic dialog that would just populate the browse tree by doing IFileSystem.fetchFileTree(), but the problem there is that you may not know how to get the IFileStore for the filesystem root.
Comment 10 Susan McCourt CLA 2009-07-09 18:21:33 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 11 Eclipse Webmaster CLA 2019-09-06 16:09:19 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.