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

Minor usability improvement in FireFTP #3

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

jzeal
Copy link

@jzeal jzeal commented Apr 24, 2012

We love FireFTP here at Web-Op-- been using it for years. When the menu gets a large number of hosts on it, we tend to want to navigate by typing in the first few characters of the host. This works well, except for hosts that start with "C" or "Q", as they fire off the Create New Account and QuickConnect dialogues. To solve this problem, I moved the Create New Account and QuickConnect commands to buttons on the far right of the toolbar, so you can happily type whatever you want in the host selection box without triggering unwanted dialogues.

It might make sense to turn this into a configurable option.

jzeal added 3 commits April 24, 2012 11:05
…n the menu. This avoids frustration when you try to navigate the hosts menu by keyboard and want to access a host starting with "c" or "q"
@mimecuvalo
Copy link
Owner

Hello Web-op!
That's awesome that you've been interested in the FireFTP code (and even cooler that you dug in and played with the source code :)

I'll have to consider these changes carefully - one of my main goals in FireFTP is keeping a clean interface, that is to say, as few buttons as possible to make it as simple for users as possible (think iPod or iPhone - with their very limited buttons). I'm actually considering moving the Connect/Edit/Abort button and Log/queue buttons out of the main toolbar and somewhere else. (the less buttons the better!)

All that being said, this brings to my attention that "C" and "Q" are difficult to reach. I will work on a design that helps mitigate this issue. I'll keep this pull request open as I develop this. Thanks for the feedback!

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.

2 participants