I was thinking that the context menu that shows up when you press keyboard shortcut for a bundle command that is overloaded (multiple commands for a single keyboard shortcut) can be quite long, especially for the git commands.
What if we (I or someone) adds a text input field to the menu which filters the menu items. And example of this can be found in Xcode [1]. Would that be a good idea?
[1] http://blog.manbolo.com/2012/05/24/filtered1.png
If you just start typing it will move the selected item (then you can just hit enter). It's not as good as the example you showed in Xcode, so that may still be useful, but it does help a lot.
On Sat, Apr 2, 2016 at 3:21 AM Jacob Carlborg doob@me.com wrote:
I was thinking that the context menu that shows up when you press keyboard shortcut for a bundle command that is overloaded (multiple commands for a single keyboard shortcut) can be quite long, especially for the git commands.
What if we (I or someone) adds a text input field to the menu which filters the menu items. And example of this can be found in Xcode [1]. Would that be a good idea?
[1] http://blog.manbolo.com/2012/05/24/filtered1.png
-- /Jacob Carlborg
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 2016-04-02 13:03, Philippe Huibonhoa wrote:
If you just start typing it will move the selected item (then you can just hit enter). It's not as good as the example you showed in Xcode, so that may still be useful, but it does help a lot.
I know about that, I still don't think it's good enough.
On 3 Apr 2016, at 17:17, Jacob Carlborg wrote:
I know about that, I still don't think it's good enough.
I’m wondering how close we are to what ⌃⌘T already does.
Main difference is that by default ⌃⌘T has more items showing (not filtered to the key equivalent pressed) and it also lack the ability to press 1-n to select the n’th item.
On 2016-04-03 14:17, Allan Odgaard wrote:
On 3 Apr 2016, at 17:17, Jacob Carlborg wrote:
I know about that, I still don't think it's good enough.
I’m wondering how close we are to what ⌃⌘T already does.
Main difference is that by default ⌃⌘T has more items showing (not filtered to the key equivalent pressed) and it also lack the ability to press 1-n to select the n’th item.
The UI is a bit more heavy. Also, since each line is taller it can't show as many lines as the context menu.
But do you think it would be better to use the same UI as ⌃⌘T but tweaked for this use case?
Honestly, almost every place where there is dropdown I wish it was a fuzzy search type box.
On 4 Apr 2016, at 16:23, Jacob Carlborg wrote:
I’m wondering how close we are to what ⌃⌘T already does.
[…] The UI is a bit more heavy. Also, since each line is taller it can't show as many lines as the context menu.
But do you think it would be better to use the same UI as ⌃⌘T but tweaked for this use case?
I’m generally a fan of unification, but in this case, it might be too much with the ⌃⌘T UI, as personally I would probably not like the bugger and more cluttered ⌃⌘T UI.
As of such, I’m not even sure I’d want a filter string, but it’s worth a try, and it could be hidden until the user actually types something.
Main downside is that we’ll be adding custom code that then need to be kept up with new OS looks.
On 2016-04-10 16:48, Allan Odgaard wrote:
I’m generally a fan of unification, but in this case, it might be too much with the ⌃⌘T UI, as personally I would probably not like the bugger and more cluttered ⌃⌘T UI.
As of such, I’m not even sure I’d want a filter string, but it’s worth a try, and it could be hidden until the user actually types something.
That's the plan.
Main downside is that we’ll be adding custom code that then need to be kept up with new OS looks.
My idea is to put an NSSearchField as the view for an NSMenuItem. I don't think any custom drawing is required.
-
Allan Odgaard -
George McGinley Smith -
Jacob Carlborg -
Philippe Huibonhoa