Bugzilla – Full Text Bug Listing
| Summary: | Should support importing into the workspace root | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Mike Wilson <Mike_Wilson> |
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | bokowski, johnjbarton, simon_kaegi |
| Version: | 0.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Mike Wilson
+1 - I find it unintuitive that you have to first create a folder that you can then import into. I agree this would be convenient. Just to record the design problem here. The URL to perform an import is currently an attribute on a file object. I.e., the UI just traverses a link on the JSON representation of a directory to perform an import. Before any file exists, the UI doesn't have a way to discover the URL of the import command. We would need something like an "import into root" attribute on the workspace object for this. Also interesting to note, Eclipse desktop also requires you to create a project before you can import a zip into it (unless the zip happens to contain an Eclipse .project file, in which case you can use a different wizard to import the project from the zip). *** Bug 369970 has been marked as a duplicate of this bug. *** Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html |