Changes between Version 6 and Version 7 of BOOK_SEARCH_R0

Timestamp:

07/22/09 15:30:24 (16 years ago)

Author:

dido

Comment:

--

BOOK_SEARCH_R0

@@ -6 +6 @@
 
 == Overview ==
-The goal of this task is to provide the ability for the user to search the content of the book. We could make this live search in some of the next revisions, for now the search will be evoked from button or enter key (while the focus is set to the text input field)
+The goal of this task is to provide the ability for the user to search the content of the book.[[BR]]
+We could make this live search in some of the next revisions, for now the search will be evoked from button or enter key (while the focus is set to the text input field)[[BR]]
+It will be nice to have the ability to search resources by their name or meta data in this palette. (From the server and from all open books). And appropriate interface for that.[[BR]]
+In this revision:
  * The Tools tab has a Search palette. It lets the user search a Sophie book.
  * A text field is available at the top of the palette where a user can enter a word or phrase he wants to find in current book.
@@ -12 +15 @@
  * Below them next and previous buttons should be available. 
  * The searching palette in the Tools tab provides a list of results with context (some words before and after the match; also the page number). 
+ * The order of the results is the following one:
+  * Results from different pages are placed from top to bottom with the order of the page number.
+  * If the results are in single page they appear sorted by the type of the component that holds them
+   * EXAMPLE: 3 results are available on the same page. One of them comes from text frame, one of them comes from embedded book and the third comes from text frame inside of a group. So on the top is the results from the text frames, after this comes the result from the group and on the bottom seats the result from the embedded book.
+  * If the results are on the same page and come from the same type of components they are ordered by the z-order of their holders.
+  * If the results come from one component they are ordered by their appearance in it.
+   * EXAMPLE: If they are 2 results inside single text frame, they should be ordered from top to bottom. The first one is the one on top etc.
+   * EXAMPLE: If the results come from embedded book the rules described above are applied to them.
 
 Typical scenario:
@@ -35 +46 @@
   * the match
   * and three (or less, applying the same rule) words after the match.
-  * If occurrences are more than 100, only first 100 should be displayed.
+  * OPTIONAL: If occurrences are more than 100, only first 100 should be displayed.
 
 == Task result ==