-
Notifications
You must be signed in to change notification settings - Fork 175
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
Add a button for leaving a channel #757
base: master
Are you sure you want to change the base?
Conversation
This adds a button to close the active channel. Signed-off-by: Andy Doan <andy.doan@linaro.org>
Only conflicting thouhgs. Nice to have, but what other buttons should we then also add? Maybe a context menu somewhere would make more sense, where we could add lots of buttons that aren't visible all the time? I fear clutter, but I agree that our interface is not nice to use with touch/mouse. |
Context menu is no good on mobile, but I have the same conflicting thoughts you do. |
Dropdown menu? |
A context menu would be great for desktop. It seems more intuitive to On Sun, Apr 3, 2016 at 10:19 AM, Magnus Hauge Bakke <
|
This feature is interesting. However I don't think that we should have buttons other than settings and exit directly in the title bar. A context menu or a dropdown seem to be the best way to provide secondary action. @lorenzhs : is the issue of the context menu on mobile an issue of triggering the context menu? Could a context menu be interesting on mobile if was triggered by a long press ? Libraries like hammerjs seem to provide an interesting way to provide long press support. If the context menu is out of question, I would go for a dropdown. However I feel like dropdowns are more suitable for choosing values in a form than triggering actions. Maybe it's only me :-) |
hmm, not sure I like the ideas of context menu on mobile. It's "hidden UI", magical features that you don't know exist until you trigger them by accident. Not sure what would work best. |
I think having the global buttons at the bottom left is counterintuitive. They won't be visible on mobile unless you open the bufferlist. If anything, I'd support the reverse (add buffer-related buttons to the bottom of the bufferlist) |
I looked at a few other apps, and some do it the way I propose. But it's super hard to design a good interface, so I'm just throwing this out as a starting point for further discussion. And not having global actions visible all the time sounds like an improvement. You still have to swipe to access channel switching, and that's a far more used action than Settings/Disconnect. |
Interesting thoughts in this thread. Would a "join channel" button conceivably have a nice place in this as well? I personally think that a "close buffer" kind of button would not be misplaced under a "buffer options" kind of button (where perhaps you could e.g. also set the notify level for the buffer?). I don't know how others use IRC but my channel list is mostly stable so I don't need this "close buffer" button in plain view (and prone to accidental pushing when fat fingering), but a way to do it without typing commands would definitely be nice (after all, if we wanted a command line we wouldn't be using GB). |
Would an action button at the bottom left be an option? The action button then opens a dialog. The dialog can be the default system dialog on mobile.
|
This adds a button to close the active channel.
Signed-off-by: Andy Doan andy.doan@linaro.org