-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Usability issues/suggestions for Project Settings dialog #1996
Comments
One more thought...This dialog really brings home to me how heavy the black background shield for modal dialogs feels. It really seems overwhelming when this relatively small dialog comes up. I wonder if we should tone the shield down in general. Also, should we consider making UI like this feel less like a modal dialog, and more like a popup attached to the gear? (I wouldn't do that as part of this user story...that would be a later story for improving dialog UIs generally, I think.) |
The shield should be toned down, in the original design comp the shield is rgba(0,0,0,0.15) |
A popover could be a good solution, but long term I think it needs to be related to the application settings story. |
@GarthDB: any thoughts on the issues in the main bug description? |
Yes, talked it over with xdid today in design review.
|
|
I mean on the project name in the panel Sent from my iPhone On Nov 1, 2012, at 8:03 AM, Randy Edmunds notifications@github.com wrote:
|
I'm not sure that makes sense--if I hover over the project name, the gear appears way to the right, and then when I move the mouse to the right to target the gear, it will dehover the project name, so the gear would disappear. We could make the hover area include the whole area to the right of the project name, but that still seems like a very fiddly interaction--as I move the mouse to the right, I have to be careful not to wobble the mouse slightly above or below the (invisible) empty hover area, or the gear will disappear. Seems like that would be very frustrating. Would it make sense to move the gear closer to the actual project name--e.g. to the right or left of the dropdown arrow? I guess the problem with that is that right now clicking on the project name actually opens the recent project list (the same as the arrow does)--I did that originally so that it was easy to target. One other thought...what if we got rid of the gear altogether, and just had the first item in the dropdown menu when you click the name of the project (or the arrow) be "Project Settings...", followed by a separator and then the recent projects list? That would be simpler and clearer, I think, and avoid the problem of having different small targets for different functionality. |
The problem is with the dropdown. If we didn't have it I would say put the |
Yup, that would be easy. |
Ok, locking it in. Project Settings in dropdown, with right click support. Final vote. |
(BTW, I'm assuming you mean that it should open on either left or right-click--not that we should only make it work on right-click.) |
Exactly Sent from my iPhone On Nov 1, 2012, at 12:47 PM, Narciso Jaramillo notifications@github.com wrote:
|
Seems like clicking on Project Settings... would probably be the exception, so what about putting it last (not first) |
I would make sure it has a divider, but it is hard to gauge which people would use more. Sent from my iPhone On Nov 1, 2012, at 12:55 PM, Randy Edmunds notifications@github.com wrote:
|
@GarthDB I assigned this to me to get started on. |
I was going to do mockup but I don't think there is any new ui. Garth Braithwaite On Friday, November 2, 2012 at 9:22 AM, Randy Edmunds wrote:
|
Forgot to address the issue with explaining what this field is. Here's a reasonably pithy explanation: "To use Live Preview with a site or application that runs on a server, enter the server URL that maps to your project folder." |
@njx should that text be:
|
Not sure--I was responding to @GarthDB who asked what the text would be so that he could figure out which of those we should do. |
If this option is added to the project dropdown, maybe it could also be added to the file menu together with live preview, as another place to find it in case the user always uses the File menu to open projects, or as the first time. |
Reviewed |
At bug review, we decided that if we thought we might want to make the first change (move the dialog from the gear into the dropdown menu), we should do that in this sprint--if we later feel like we want the gear back, it makes more sense to split it out later, rather than conversely starting with the gear and then taking it away. So I'll review the pull request and merge as much as is already done. The other issues (help text, project name in dialog) can be done later. |
Adding sprint 16 back (for the first part of the issue). |
OK, the first two issues were fixed by #2034. We can fix the last one later. |
Removed Sprint 16 tag for remaining issue. |
Changing to low priority for remaining issue. |
@larz0 We were waiting to here from Garth about his thoughts on Usability suggestion 3, so re-assigning to you. |
Thanks @redmunds What does the dialog look like right now? |
@larz0 Invoke the dialog using: File > Project Settings... |
I like the idea of making "Project Settings…" the first item in the drop-down with a separator. |
The wording of the current text ("(to use a local server, specify url)") is meant to indicate that this field is optional and why it would be used. What about: "(to use local server, specify url such as: http://localhost:8000/)" ? |
Sounds good. We should remove the parentheses and capitalize the "T" in "to". |
Hey Lars, I'm wondering why you're signed up for the Brackets repo with @larz0 , but you're signed up with the Edge Code repo with Update: On Edge Code it's internal-only @lhsu (https://git.corp.adobe.com/lhsu). Yeah it's confusing... |
Minor wording tweak suggestion: "To use a local server, enter a url like http://localhost:8000/" |
@redmunds: I've always had larz0 on github.com but github enterprise won't let me use the same username so I've changed my name to "lhsu aka larz0 on GitHub.com" on github enterprise :) |
@njx we should go with that word tweak. |
@larz0 No worries. After I made that comment I realized that we all have to use external ids for brackets and internal ids for edge code, so I guess it's a fact of life. |
To be safe, FBNC back to @njx . |
Originally I was thinking that we would have some more extensive help text in here (accessible via a tooltip or some such). But I haven't heard that people are confused by the current dialog, and the new placeholder text seems better, so there isn't much value in keeping this bug open, I think. |
The text was updated successfully, but these errors were encountered: