[haiku-development] Re: TrackerGrep [was Re: missing -lm?]

Ingo Weinhold wrote on Fri, 02 May 2008 18:30:04 +0200:
> On 2008-05-02 at 17:29:05 [+0200], Ryan Leavengood <leavengood@xxxxxxxxx> 
> wrote:
> > On Fri, May 2, 2008 at 11:00 AM, Stephan Assmus <superstippi@xxxxxx> wrote:
> > >
> > > I cannot comment on the other issues, but this reminded me of a question I
> > > wanted to bring up: I think TrackerGrep is great and IMHO it could be part
> > > of the base Haiku distro. I looked at the code and it is clean and easy to
> > > follow. I would like to extend the app to support node monitoring for 
> > > every
> > > listed file, so that the list adapts live to any changes you do to these
> > > files as soon as you change them. I guess that would be another nice 
> > > feature
> > > when doing Haiku demos.
> > 
> > I think that idea is fine and support it.
> > 
> > What would also be good is to add some indexing of files, a la Beagle,
> > Spotlight and all that. Though that is certainly a lot more work than
> > just adding TrackerGrep.
> 
> This is definitely a must have, though not for R1. We will probably implement 
> the indexing in a separate server. The most interesting question is how to do 
> that in a fast way. We might need to add some special FS support for it.

That's one way of doing it.  And fairly safe.  Another way is to have
attributes which contain multiple elements.  I did some experiments with
that, using space separated strings interpreted as a list of keywords.
It fitted in with the current system fairly well.

The applications (or a background thread running a Translator) would have
to be adapted to write a standard "META:keywords" attribute with all the
keywords for a modified document.

The file system would need only a few changes.  When adding an attribute
to the index, each word in the attribute is added separately to the index,
with a back pointer to the file as usual.  Thus the file is in the index
multiple times.  Deleting the keywords is similar to adding.  Searching
(and live queries) is a bit different, since you may get the same file
multiple times.  The simple solution is to have user level code filter
out the duplicates.

- Alex

Other related posts: