Bugzilla – Full Text Bug Listing
| Summary: | [client] Organize import/export commands in navigator | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | John Arthorne <john.arthorne> |
| Component: | Client | Assignee: | Susan McCourt <susan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | tomasz.zarna |
| Version: | 0.2 | ||
| Target Milestone: | 0.2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
John Arthorne
On bug 347194 I was looking for "Download as ZIP" action in the context menu in the Navigator. Didn't notice the arrow next to it. This could be adjusted at the same time here, I think. (In reply to comment #1) > On bug 347194 I was looking for "Download as ZIP" action in the context menu in > the Navigator. Didn't notice the arrow next to it. This could be adjusted at > the same time here, I think. +1. Now that the SFTP import/export are grouped together, I've been looking for it there, too. I have another bug talking about reorganizing/grouping those commands, i'll move this to M8 and look at all the commands together. The "download" icon was moved to the menu and named "Export as zip." After MUCH discussion with John, McQ, Boris, graphic designers...about the terminology we were using, we decided: - we are having troubles because we have never named the "workspace" for the user. So using terms that suggest "in" and "out" beg the question. Into what? Out of what? Some apps, including Mac apps, are starting to use terms like "Add to Library" rather than "import." But we don't have a noun. (Add to workspace?) - McQ felt like import/export implies a data conversion. We are doing a conversion for zips, but not for SFTP. - Upload/download is a huge can of worms. Various jargon dictionaries define upload as "to the bigger device, to the farther away device, " etc. Getting too focused on the up/down direction seems troublesome, since our workspace is actually in the cloud and whether we are working with a local machine has less relevance. - SFTP could almost be considered a copy. There is no data transform happening, so it's not really import/export. We finally settled on "Transfer" as the generic terminology and SFTP as the specific. Bottom line: There are many ways to group the commands. For example "Copy to..." (workspace copy) "Copy to remote..." (SFTP) Transfer to remote... (SFTP) Push to remote... (Git) Import zip Import using SFTP For 0.2, we decided to use very specific terminology for the zip and SFTP case and not try to group with move/copy or import/export. So we ended up with: SFTP from... SFTP to... Import from zip... Export to zip... We know this will become more generic, but sorting out "import" vs. "transfer" vs. "copy" won't make sense until: - we have more use cases and/or - we are willing to name the target (workspace) |