shared wasabi implementation
Mikkel Kamstrup Erlandsen
mikkel.kamstrup at gmail.com
Thu Feb 15 13:52:59 PST 2007
2007/2/15, Fabrice Colin <fabrice.colin at gmail.com>:
> On 2/15/07, Jos van den Oever <jvdoever at gmail.com> wrote:
> > Hello wasabi people,
> > Shouldnt we start sharing parts of the code required to implement
> > wasabi? I'm mainly thinking about a struct in c representing a parsed
> > wasabi query and functions to de- and serialize these from either the
> > xml or the user language.
> > This should be no more than a couple of files that we can put in an
> > xsd svn. Requirements to make it palletable for most: few deps and
> > written in c. For C++ fans we can add a small wrapper.
> > What do you think? Can someone here open an svn project for this?
> Jean-Francois and I have started a side project called Dijon, with the aim
> of facilitating code sharing between Recoll and Pinot. Our first target is
> filters, but this should eventually cover anything that comes out of the
> Wasabi project, which is actually why we chose the name Dijon ;-)
> The project's SVN repo is at http://svn.berlios.de/wsvn/dijon
> There's a mailing list at
Great to hear! I like the name :-)
Do you have any plans for a standard way of installing new filters? Wasabi
could use this (as has also been mentioned on Gnomes desktop-devel-list).
I've been discussing it a bit with various people on how to standardize
this, but it is tricky business. In some cases it is enough to specify hpw
to index files matching a particular pattern, but there are also cases like
emails residing in a database in a hidden directory, indexing of web pages
as you browse etc...
Both of us have been extremely busy lately and have not been able to
> work on it that much. Anyone willing to tuck in, for instance with
> toolkit neutral parsers for the query languages, get in touch.
I think it would also be a good idea to wait atleast until after Fosdem
before pouring many hours into any code. I will be hyping Wasabi as much as
possible and hope to get some useful critique/input there.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the xdg