On Aug 2, 2006, at 12:35 PM, John Anderson wrote:
Hi Mimi:
Is this a correct restatement of your spec, assuming we go with
modeless search?
Whenever the user types something in the search box we switch the
summary view display to a table
view (dashboard) and display the results of the search.
I would distinguish table view from dashboard. I don't think we want
to section search results by triage status.
The search is over all items in all sidebar collections in the
selected application area. If any visible attribute of an item
matches the search string, the item is displayed.
Correction: Only item matches in the currently selected collection
are displayed. You have to select a different collection to see the
search results in that collection. Switching collections in the
sidebar does not automatically end the search session.
Each collection in the sidebar displays a number of matches, e.g.
Home(3).
If possible, but the # feedback isn't a requirement for the first pass.
If search is slow we will add an "X" toggle icon to stop/start the
search, and will provide feedback indicating the search is proceeding.
We want to have the X present at all times...whether or not it is
search. This allows people to end the search session without having
to select all the text and hit delete.
If there is no text field is actively being edited, typing changes
the focus to the search box and starts editing.
Correct.
I have two more questions:
1) When you say that all collections in the application area are
searched, does that include all the "Out of the Box" collections,
e.g. Dashboard?
2) Should there be separate search strings for each application
area? Suppose you launch a new Chandler for the first time, search
in "tasks", then switch to calendar view. Does it search Calendar
with the task search string, or display a Calendar view? I think it
seems better to have separate search strings for each application
area.
This depends on which of the following is more common:
1. I'm looking for something that mentions Brown University, not sure
if it was a Task item or just a Note or directions in the notes field
of an Event (in which case, we want the user to be able to easily
switch between app areas without having to re-type the same search
string); OR
2. Each app area has very different search scenarios and search
sessions rarely go across app areas.
I'm inclined to go with the 1st, although I'm prepared to reverse 180
degrees on this hunch. Is it hard to change after the fact?
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
