On Wed, 31 Jan 2007, [EMAIL PROTECTED] wrote:
From: D John Anderson <[EMAIL PROTECTED]>
Subject: [Design] Search
I also think putting find functionality in a quick entry command
seems to violate another basic rule of UI design: Don't hide
important commands from your user. Nobody's going to figure out that
you need to type "/search" to do a search. Even with command type
ahead, nobody is going to discover it. As an aside, I spent over a
week trying to implement Darshana's command type ahead in the
toolbar, and got really close, but still have a difficult bug holding
it up on Mac. I'm not sure I'll succeed in finishing it for Preview.
To make it possible to actually discover Chandler's full text search feature,
I added a "Find" menu item under "Edit" as is normally done.
This menu item (also works with Command-F), enters /find into the search bar
and sets input focus to it. One can type Command-F <string to find> <return>
and the search happens.
And I renamed /search to /find which is shorter, easier to type, and
consistent with this new menu item.
I think both these changes make this feature more usable. These can be changed
or reverted, of course... comments are welcome !
John, there is a bug with search currently: the search results seem to stick
around. If I enter a new - more restrictive - search, the old results are
still included in the search results.
Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
