The little search bar in the Dock is a delightful tool that saves so much time it's ridiculous.
*Except* for the way that typing in a phrase that happens to exactly match a known message results in a browser on *only* that exact message. That annoys me pretty much every time because almost every time I was actually wanting the MessageList with the matches for the phrase.
There is a trivial solution to this, requiring us simply to delete the mid-method clause starting with `Symbol hasInterned: input ifTrue: ` Yes, I suppose we could add YetAnotherPreference but we already have about ten times more than is sensible. Alternatively perhaps making it shift-key dependent - one way includes the full match aspcet, the other avoids it - might suit people better.
What do you think?
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim egret - apology by email
Just fyi, I believe you can get the behavior you're looking for by pressing [Cmd+b] instead of [Enter].
I want to replace the Search bar with opening a balloon at the hand which is just a workspace "scratch pad" for searches, calculator, quick expressions, and "recent history". There and back, all without having to touch the mouse. And since it expands dynamically, I can see all the contents, unlike the search bar.
- Chris
On Fri, Aug 6, 2021 at 6:18 PM tim Rowledge tim@rowledge.org wrote:
The little search bar in the Dock is a delightful tool that saves so much time it's ridiculous.
*Except* for the way that typing in a phrase that happens to exactly match a known message results in a browser on *only* that exact message. That annoys me pretty much every time because almost every time I was actually wanting the MessageList with the matches for the phrase.
There is a trivial solution to this, requiring us simply to delete the mid-method clause starting with `Symbol hasInterned: input ifTrue: ` Yes, I suppose we could add YetAnotherPreference but we already have about ten times more than is sensible. Alternatively perhaps making it shift-key dependent - one way includes the full match aspcet, the other avoids it - might suit people better.
What do you think?
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim egret - apology by email
On Sat, 7 Aug 2021 at 03:06, Chris Muller asqueaker@gmail.com wrote:
I want to replace the Search bar with opening a balloon at the hand which is just a workspace "scratch pad" for searches, calculator, quick expressions, and "recent history". There and back, all without having to touch the mouse. And since it expands dynamically, I can see all the contents, unlike the search bar.
The search bar is discoverable, at the expense of screen space. How might a user discover such a balloon?
(I have a pet hatred of interfaces that aren't discoverable. iOS and Android - particularly iOS - drive me crazy.)
Cheers,
- Peter
I know what you mean, but a clear definition of "discoverable" would help. For example, I don't think you mean putting it in the help pages. Probably you mean something like a traditional "find" icon (magnifying glass) button could replace the current search field, where clicking it would open the balloon..
On Sat, Aug 7, 2021 at 2:19 AM Peter Crowther peter@ozzard.org wrote:
On Sat, 7 Aug 2021 at 03:06, Chris Muller asqueaker@gmail.com wrote:
I want to replace the Search bar with opening a balloon at the hand which is just a workspace "scratch pad" for searches, calculator, quick expressions, and "recent history". There and back, all without having to touch the mouse. And since it expands dynamically, I can see all the contents, unlike the search bar.
The search bar is discoverable, at the expense of screen space. How might a user discover such a balloon?
(I have a pet hatred of interfaces that aren't discoverable. iOS and Android - particularly iOS - drive me crazy.)
Cheers,
- Peter
Hi all --
[Chris] Just fyi, I believe you can get the behavior you're looking for by pressing [Cmd+b] instead of [Enter].
Tim wants to see the "Message Names" tool even if the query string matches a known symbol. On my machine for exact matches, [CMD]+[B] behaves the same way [ENTER] does in the search bar: class browser for classes, implementors tool for methods.
[Chris] I want to replace the Search bar with opening a balloon at the hand which is just a workspace "scratch pad" for searches, calculator, [...]
Reads like a Workspace with some interesting conveniences. Nothing too special. Not really like a "new" tool. :-)
[Tobias] Just add a * at the end of the phrase?
That's my workaround, too. But you would also need to add a * at the beginning for the entire result list.
For exact matches I still tend to use any text buffer other than the search bar. That's why the search-bar's behavior is also unexpected for me. :-) Yet, I know that it is considered a feature.
Well, we could vote that feature out of the system. :-D BUT: Typing the beginning, completing it with CMD+Q and then hitting ENTER wouldn't work anymore. :-O
Best, Marcel Am 09.08.2021 01:19:09 schrieb Chris Muller asqueaker@gmail.com: I know what you mean, but a clear definition of "discoverable" would help. For example, I don't think you mean putting it in the help pages. Probably you mean something like a traditional "find" icon (magnifying glass) button could replace the current search field, where clicking it would open the balloon..
On Sat, Aug 7, 2021 at 2:19 AM Peter Crowther wrote:
On Sat, 7 Aug 2021 at 03:06, Chris Muller wrote:
I want to replace the Search bar with opening a balloon at the hand which is just a workspace "scratch pad" for searches, calculator, quick expressions, and "recent history". There and back, all without having to touch the mouse. And since it expands dynamically, I can see all the contents, unlike the search bar.
The search bar is discoverable, at the expense of screen space. How might a user discover such a balloon?
(I have a pet hatred of interfaces that aren't discoverable. iOS and Android - particularly iOS - drive me crazy.)
Cheers,
- Peter
On 7. Aug 2021, at 01:17, tim Rowledge tim@rowledge.org wrote:
The little search bar in the Dock is a delightful tool that saves so much time it's ridiculous.
*Except* for the way that typing in a phrase that happens to exactly match a known message results in a browser on *only* that exact message. That annoys me pretty much every time because almost every time I was actually wanting the MessageList with the matches for the phrase.
There is a trivial solution to this, requiring us simply to delete the mid-method clause starting with `Symbol hasInterned: input ifTrue: ` Yes, I suppose we could add YetAnotherPreference but we already have about ten times more than is sensible. Alternatively perhaps making it shift-key dependent - one way includes the full match aspcet, the other avoids it - might suit people better.
What do you think?
Just add a * at the end of the phrase? Just my 2ct…
Best regards -Tobias
tim
squeak-dev@lists.squeakfoundation.org
-
Chris Muller -
Marcel Taeumel -
Peter Crowther -
tim Rowledge -
Tobias Pape