Community
Participate
Working Groups
The org.eclipse.ui.internal.ide.misc.ResourceAndContainerGroup class is used in a lot of wizards. In many cases it would be useful to be able to create a new folder, yet this is not supported. Please consider adding a "New Folder" tool; see the attached mock-up. Thanks.
Created attachment 125063 [details] Screenshot/mock-up
This would be a very cool enhancement :D
Simon, new folder creation is in fact already supported :o In your mockup, if you'd typed org.equinoxosgi.toast.backend.controlcenter/src/org/equinoxosgi/foo/bar it would have actually created the file typed in the "File Name:" field into the foo/bar folder...! Anyways, I totally agree that a new folder icon would be cool :)
That's a great tip. The ability to add folders is really not visible enough, especially since neither I nor Chris had spotted it! So yeah, the addition of a New Folder tool would be perfect, and hopefully simple to do! Thanks, Benjamin. Can we expect this in time for 3.5?
(In reply to comment #1) > Created an attachment (id=125063) [details] > Screenshot/mock-up For the record, that toolbar is created by a DrillDownComposite.
Right, DrillDownComposite does contain the current tools, I noticed that too. But, I was not convinced that a "New Folder" should be considered a "drill down" tool like "Home", "Back" and "Go Into". Possibly the answer is to rename DrillDownComposite as we add the "New Folder" tool.
(In reply to comment #6) > Possibly the answer is to rename > DrillDownComposite as we add the "New Folder" tool. The DDC class is public API. You don't _literally_ mean "rename", right?
Sorry, I'm going from memory, so clearly renaming API is not my intention. Nevertheless, adding "New Folder" to the composite sounds like a mismatch, but let's leave that to the committer to decide. :-)
(In reply to comment #4) > Can we expect this in time for 3.5? http://wiki.eclipse.org/Platform_UI/How_to_Contribute
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.