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

Rename "Preferences" pane in Preferences window to "General" #1306

Closed
Sesquipedalian opened this issue Dec 31, 2012 · 5 comments
Closed

Rename "Preferences" pane in Preferences window to "General" #1306

Sesquipedalian opened this issue Dec 31, 2012 · 5 comments
Assignees

Comments

@Sesquipedalian
Copy link

QS's Preferences window contains a pane that is also called Preferences. This may seem like a fairly minor violation of normal HID guidelines, but it is potentially confusing to the user, and a perpetual annoyance for people offering support on the discussion group (or at least me). The pane ought to be renamed General, in compliance with standard practice.

Almost every time I have to explain how to change their QS preferences to someone on the support group, I have to say something like "Click on the Preferences tab within Quicksilver's Preferences window, then..." This is confusing to readers and annoying to type every time. If the pane were renamed General, I could simply say "In QS's General Preferences..." and the user would understand me correctly.

I expect that this would be a pretty trivial change to make, and it would make users less confused and me happier giving support. :)

@skurfer
Copy link
Member

skurfer commented Dec 31, 2012

Agreed, though I might prefer something like "Settings". "General" implies that there are other types of preferences under the other panes, when really, there aren't any traditional "preference" items (to control application behavior) there.

@ghost ghost assigned skurfer Dec 31, 2012
@Sesquipedalian
Copy link
Author

Well, "General" seems to be the standard practice, and I don't think it would cause the sort of confusion you are worried about. The Triggers, Catalog, and Plugins panes do control application behaviour, after all, and they are very clearly labelled. They seem fairly analogous to the Rules and Accounts panes in Mail and the Extensions pane in Safari, and having the latter panes in those applications alongside a General pane doesn't cause any confusion for users.

But at any rate, if we can stop having "Preferences" inside of "Preferences", I'll be happy. :)

Jon

On 2012-12-31, at 3:50 PM, Rob McBroom notifications@github.com wrote:

Agreed, though I might prefer something like "Settings". "General" implies that there are other types of preferences under the other panes, when really, there aren't any traditional "preference" items (to control application behavior) there.


Reply to this email directly or view it on GitHub.

@pjrobertson
Copy link
Member

Personally, I'd prefer 'General', but I'm not too fussed.

Definitely something that needs changing, @hmelman probably won't be happy
though as he'll probably have to change his manual a little ;-)

On 31 December 2012 21:11, Sesquipedalian notifications@github.com wrote:

Well, "General" seems to be the standard practice, and I don't think it
would cause the sort of confusion you are worried about. The Triggers,
Catalog, and Plugins panes do control application behaviour, after all, and
they are very clearly labelled. They seem fairly analogous to the Rules and
Accounts panes in Mail and the Extensions pane in Safari, and having the
latter panes in those applications alongside a General pane doesn't cause
any confusion for users.

But at any rate, if we can stop having "Preferences" inside of
"Preferences", I'll be happy. :)

Jon

On 2012-12-31, at 3:50 PM, Rob McBroom notifications@github.com wrote:

Agreed, though I might prefer something like "Settings". "General"
implies that there are other types of preferences under the other panes,
when really, there aren't any traditional "preference" items (to control
application behavior) there.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1306#issuecomment-11784093.

@Sesquipedalian
Copy link
Author

If Howard is going to be annoyed, I'm sure he is far more concerned about dealing with all the plugins you've added, deprecated, or completely rewritten. ;)

Jon

On 2012-12-31, at 4:42 PM, Patrick Robertson notifications@github.com wrote:

Personally, I'd prefer 'General', but I'm not too fussed.

Definitely something that needs changing, @hmelman probably won't be happy
though as he'll probably have to change his manual a little ;-)

On 31 December 2012 21:11, Sesquipedalian notifications@github.com wrote:

Well, "General" seems to be the standard practice, and I don't think it
would cause the sort of confusion you are worried about. The Triggers,
Catalog, and Plugins panes do control application behaviour, after all, and
they are very clearly labelled. They seem fairly analogous to the Rules and
Accounts panes in Mail and the Extensions pane in Safari, and having the
latter panes in those applications alongside a General pane doesn't cause
any confusion for users.

But at any rate, if we can stop having "Preferences" inside of
"Preferences", I'll be happy. :)

Jon

On 2012-12-31, at 3:50 PM, Rob McBroom notifications@github.com wrote:

Agreed, though I might prefer something like "Settings". "General"
implies that there are other types of preferences under the other panes,
when really, there aren't any traditional "preference" items (to control
application behavior) there.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1306#issuecomment-11784093.


Reply to this email directly or view it on GitHub.

@hmelman
Copy link

hmelman commented Jan 2, 2013

I'm okay with General. Though I've never had a problem with saying "in QS's Application Preferences" or "QS's Command Preferences". If it were General I'd have to say "In QS's General Preferences under Command".

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

No branches or pull requests

4 participants