Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(ux): move preferences to menubar #1425

Merged
merged 4 commits into from
Apr 24, 2020
Merged

feat(ux): move preferences to menubar #1425

merged 4 commits into from
Apr 24, 2020

Conversation

hacdias
Copy link
Member

@hacdias hacdias commented Apr 18, 2020

This PR removes the Desktop settings from the Web UI panel! Related to #1389.

Screenshot 2020-04-18 at 18 45 44

License: MIT
Signed-off-by: Henrique Dias hacdias@gmail.com

@hacdias hacdias requested review from lidel and jessicaschilling and removed request for lidel April 18, 2020 17:46
@hacdias hacdias marked this pull request as ready for review April 18, 2020 17:46
@hacdias hacdias mentioned this pull request Apr 18, 2020
22 tasks
@hacdias hacdias changed the title feat: add preferences to menubar feat(ux): move preferences to menubar Apr 18, 2020
Copy link
Contributor

@jessicaschilling jessicaschilling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice 😊 Suggested some text tweaks and also one question. In your screenshot, it looks like both shortcuts are enabled, but the "Enable ..." menu items are still visible. Should they say "Disable ..." in that scenario? I'm a little unclear how the user disables these.

assets/locales/en.json Outdated Show resolved Hide resolved
assets/locales/en.json Outdated Show resolved Hide resolved
"ipfsOnPathInstall": {
"title": "Install IPFS on PATH",
"message": "By enabling this option, IPFS will be available on your command line as \"ipfs\". This action is reversible.",
"action": "Install"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For both the dialog boxes (and their menu items) related to IPFS on PATH, we're using "install/enable" and "uninstall/disable" interchangeably, which is a little confusing. Let's decide on either install/uninstall or enable/disable and be consistent throughout ... I might go for enable/disable so that it feels more like an option rather than something more severe, but there might be precedence for install/uninstall elsewhere that I'm unaware of?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just updated everywhere to enable/disable that is not related to IPFS Desktop updates 😃

I might go for enable/disable so that it feels more like an option rather than something more severe

Agreed. We're not actually installing anything but when updating or enabling npm on IPFS, which I will make more clear.

assets/locales/en.json Outdated Show resolved Hide resolved
assets/locales/en.json Outdated Show resolved Hide resolved
assets/locales/en.json Outdated Show resolved Hide resolved
assets/locales/en.json Outdated Show resolved Hide resolved
assets/locales/en.json Outdated Show resolved Hide resolved
assets/locales/en.json Outdated Show resolved Hide resolved
@hacdias
Copy link
Member Author

hacdias commented Apr 18, 2020

@jessicaschilling thanks for pointing that out. They’re actually not enabled. Those options enable them globally. They are checkboxes.

Now that I think of it, being a checkbox and having a verb (“Enable...”/“Disable...”) does not seem to be a great idea.

Either we keep the checkbox and remove the verb (simpler solution) or we toggle between verbs (Enable and Disable).

Checkbox tick example:

image

Here's an example of a mac app I use (Lungo) whose preferences are just checkboxes:

image

@jessicaschilling
Copy link
Contributor

Checkboxes are good! If unchecked, do “take screenshot” and “disable hash” menu items act accordingly (do the shortcuts disappear)?

@hacdias
Copy link
Member Author

hacdias commented Apr 18, 2020

Checkboxes are good! If unchecked, do “take screenshot” and “disable hash” menu items act accordingly (do the shortcuts disappear)?

The shortcuts always work if the menu is open. That’s why they’re visible. The preferences enable them globally, ie, even with the menu closer, you can press them and they’ll work. I guess we should find a better way to pass that message.

@jessicaschilling
Copy link
Contributor

OH ... got it. Sorry! Good point though; I was confused, others will be too.

We don’t actually need “Enable” in menu items - the checkboxes imply it (see your Lungo example). Removing it would allow room for “Global Screenshot Shortcut” and “Global Download Shortcut”, which might be more explicit. Would like to run that past @lidel though.

@hacdias
Copy link
Member Author

hacdias commented Apr 18, 2020

Yes, I agree we should wait for @lidel opinion on this 😃

@hacdias
Copy link
Member Author

hacdias commented Apr 19, 2020

image

@hacdias hacdias force-pushed the feat/preferences branch 5 times, most recently from 1ca47ca to 869c28c Compare April 19, 2020 09:26
@hacdias
Copy link
Member Author

hacdias commented Apr 20, 2020

Just as a thought: I wonder if some of the 'Advanced' things shouldn't be moved under Preferences. The only one that doesn't make much sense to me would be 'Run Garbage Collector'. All the others seem to fit under Preferences. Wdyt? (We can leave this to another PR if this one is good)

image

@jessicaschilling
Copy link
Contributor

@hacdias - I'd be inclined to leave these under "Advanced" ... to a certain degree, they're sort of applicable to being considered preferences ... but only to advanced users. ;)

Copy link
Member

@lidel lidel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Labels look okay. Would keep "Advanced" as-is for now.
Small concern below tho.

@@ -16,7 +16,7 @@
"readReleaseNotes": "Read Release Notes",
"status": "Status",
"files": "Files",
"settings": "Settings",
Copy link
Member

@lidel lidel Apr 21, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing this from the top level menu may be a problem. I believe users will look for the "WebUI Settings" screen under "Settings" and won't find any entry point there.

Can we add it at the very top of new "Settings" submenu, to maintain continuity, of sorts?

One entry followed by a separator and then existing entries under "Desktop" header (similar to existing "Experiments"):

2020-04-21--03-12-26

@jessicaschilling Does this make sense? If so, what would be the correct wording here: "Open Node Settings"? "Open WebUI Settings"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just rebased on top of master and added a "Open Node Settings" which opens Web UI settings:

image

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great. Agree on “Node Settings” over “WebUI settings sine the thing you’re adjusting is the node itself.

Copy link
Member

@lidel lidel Apr 21, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about adding Desktop Integrations header below the separator,
to make the grouping even more clear?

png

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just added:
image

Just wondering if it's really needed. But looks great

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having a clarification of “these are the prefs for this app” is a good idea. I might just say “App Preferences” though? Not sure if “desktop integrations” makes sense unless you’re already deeply familiar.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lidel what do you think?

@hacdias
Copy link
Member Author

hacdias commented Apr 22, 2020

@lidel other than the the 'Desktop Integrations' label, is there anything you'd change?

@hacdias
Copy link
Member Author

hacdias commented Apr 22, 2020

Just renamed 'Desktop Integrations' to 'App Preferences'

image

@jessicaschilling
Copy link
Contributor

LGTM, but let's get @lidel's blessing first 😊

@hacdias
Copy link
Member Author

hacdias commented Apr 22, 2020

Yes!

License: MIT
Signed-off-by: Henrique Dias <hacdias@gmail.com>
License: MIT
Signed-off-by: Henrique Dias <hacdias@gmail.com>
License: MIT
Signed-off-by: Henrique Dias <hacdias@gmail.com>
License: MIT
Signed-off-by: Henrique Dias <hacdias@gmail.com>
@hacdias
Copy link
Member Author

hacdias commented Apr 23, 2020

@lidel I decided to fix #1436 because those links enable the user to access IPFS Desktop settings unless this one gets merged.

Copy link
Member

@lidel lidel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks! (no strong feeling about labels, just wanted to have the option in menu 👍)
Feel free to merge if nothing else is needed here.

@hacdias hacdias merged commit dfad823 into master Apr 24, 2020
@hacdias hacdias deleted the feat/preferences branch April 24, 2020 07:01
hacdias added a commit that referenced this pull request Sep 1, 2022
SgtPooki pushed a commit that referenced this pull request Oct 3, 2022
* chore: remove old event handler removed in #1425

* refactor: use ipcMainEvents constant
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Disable WebUI links in "IPFS is Not Running" state
3 participants