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

UX improvements to settings - unsaved reminder, save button placement, paths validation #438

Open
1 task done
luckedea opened this issue Nov 20, 2024 · 0 comments
Open
1 task done
Assignees
Labels
enhancement New feature or request

Comments

@luckedea
Copy link
Member

luckedea commented Nov 20, 2024

Is there already an issue for this request?

  • I have checked older issues, open and closed

Platform

All

Describe the enhancement you'd like

Purpose

NZBGet's UI is quite unfriendly to troubleshooting and new users, this issue is mostly based on community feedback from github and discord. NZBGet should stay fast and clean, however there's no harm if we improve user experience, at least in small steps.

Proposed changes

Unsaved reminder

Currently if you make changes to settings, mostly PATHS configurations and NEWS SERVERS changes - the fact the changes need to be saved isn't communicated to the user, even through tabs cycling (within settings), and you are only reminded if you are leaving Settings. Which is not great if you are working on configurations, and you forgot to click "SAVE" because the button is not visible.

So if there are unsaved changes:

  • Show "unsaved" near the modified field
  • Move the save button so it's more visible
  • Suggest changes if user switched between settings tabs too

Save button positioning

Related to previous request - if there are unsaved changes, a more visible save button is a must. Either move it up permanently, or duplicate it at the top on unsaved changes.

Paths validation

NZBGet can be a bit confusing on paths, especially if download and intermediary paths are on network storage, on removable media. On various platforms the slashes in paths are different, and sometimes you can't easily test it.

When user makes changes to the path, add a button/icon/function to validate it, results can be:

  • path found, it's writeable
  • path found, it's not writeable
  • path not found, path would be created on restart
  • path not found, path can't be created

No active news servers available

I install nzbget a lot, and this default my.newsserver is just killing me, it's there but you kind of forget about it sometimes. Competitors have a wizard to add it upon installation, some good software shows a red exclamation mark if something critical is not configured.

If there are no news servers configured, and default my.newsserver isn't considered, please show a red [1] near the Settings tab, and News Servers under Settings (so it's clear what's the warning about).

Extra information

No response

@luckedea luckedea added the enhancement New feature or request label Nov 20, 2024
@dnzbk dnzbk self-assigned this Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants