On 2012-12-16 08:37, Maxim Khitrov wrote:
As with the
stand-alone wiki pages, I would only index the last version of
each matching file in each branch. When a file is changed by a new
check-in or push, remove the old version and index the new one.
Finally, how should the results be presented? Perhaps the simplest
solution is to only show one type of results on a single page.
Just as you have Tickets Only, Wiki Only, and other buttons on the
current timeline page, the search results can default to the
timeline view, where the user could then click buttons to search
for other type of information (Tickets, Wiki, and Files).
Thoughts?
Given it's an index, it would make sense not to transfer its content
when syncing between repositories, as it can be regenerated from
repository content; and a full-text index has the potential to easily
exceed the size of the indexed data. On the flip-side, information on
what results were considered to be most relevant to a supplied search
criteria would be something interesting to collect and share between
repositories that are using full-text search to improve the global
utility of search.
I think I would want to be able to choose to:
* Index nothing (the default)
* Index only the latest versions of wiki pages, tickets and files in trunk
* Index only the latest versions of wiki pages, tickets and files in
all branches
* ...other possible combinations of what/when to index?
* Index everything, everywhen
If the search box appears on each screen, I agree that the most
unsurprising thing would be to search only the latest version of the
kind of item within the branch that's being displayed, with the option
to expand the search in terms of kind, time, and (possibly) branch.
--
Martin Rudat
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
