THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Wiki Markup |
|---|
The results will be displayed using a tree layout, something like Eclipse IDE does \[see image below\] on its text search results, but instead of a tree like project \-> package \-> class \-> fragment text that contains the searched text, it would be, for example, node > contribution > component > file.componsite file > fragment text that contains the searched text. This is just an example, the way the results can be displayed can still be discussed on the community mailing list.!eclipse-search-example.png|align=center! If the results is contained inside an artifact that is text file, when the user click on the result tree leaf, the complete text file will be displayed containing the highlighted text. If it's not an text file, for example, if the result is the name of a jar file, clicking on the result tree leaf the jar file will be opened (downloaded). When displaying a result, if a file reference is in it, it could be displayed as a link to the file, as suggested by Luciano Resende at [http://markmail.org/message/ugldeod4u54nknz5]. |
By default, the results returned by Lucene are sorted by a score that is assigned to each result using a predefined heuristic, this is considered to be one of the best ways to show the results, because it considers the word frequency in the index and some other variables to define if a result is relevant or not. However, the way the results are sorted and scored also can be discussed on the community mailing list.
...
April 20 - 27: getting familiar with Tuscay SCA code and setting up environment
April 28 - May 1226: Implementing text and file analyzer for indexing
May 13 27 - 27June 10: Implementing indexing phase
May 28 11 - June 518: Implementing searching phase
June 6 June19 - 27July 3: Implementing results tree
June 28 4 - July 1218: Implementing full result display
July 13: Mid-term evaluation
July 14 29 - July 28August 5: Implementing results highlighting
July 29 August 6 - August 810: Performance adjustments
August 9 11 - 16: Documenting and writing test cases
...