Summary: | [Search] Participants should surface in search progress | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> |
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.0 | ||
Target Milestone: | 3.1 M2 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Philipe Mulet
2003-12-09 07:23:31 EST
Use SearchParticipant.getDescription() Not for 3.0 Reopening Search engine performs search in 2 main steps. 1) Lookup for potential documents in indexes 2) Locate exact and/or potential matches in these documents So, we'll create a new SubProgressMonitor and initiate 2 subtasks for these 2 steps. Progress monitor dialog will have an additional text under progress bar: 1) {0}: looking for indexes... 2) {0}: locating matches... where {0} will be search participant description (currently "Java" for JavaSearchParticipant) Bar progression has been reviewed to be as appropriate as possible whatever the number of found matches: - items total is the number of indexed documents with possible matches we got in step 1. - number of increments will be volontary limitated due to the fact that refreshing progress bar may consume lot of time during the search. For example, refresh progress bar for each document multiplies search time by 4!... The rule for increments number will be: + 0-399: 2 + 400-599: 3 + 600-999: 4 + >1000: (total/1000) * 5 This rule will make time to refresh progress bar small regarding to global search time... Fixed and released in HEAD. No test case added as it concern Progress dialog... Only verify that all JDT/Core and JDT/UI tests pass. Additional messages have been modified as follows: 1) {0}: lookup indexes... 2) {0}: locate matches... Verified in I200409230100. |