[Mono-docs-list] monodoc status?

[Miguel de Icaza]

Hello,

> > I might consider using it, yes.  But I am a bit behind there ;-)
> 
> It is arguably the best search library available for Java, but I haven't
> looked in detail at the dot net port.

Well, that is very good news ;-)

> > > Where can I read up on the evolution searching library? Does it have any
> > > white papers/articles, API docs you could point me at?
> > 
> > None of that sort, you would have to read the source code ;-(
> 
> Hmmm. I suspect reading C source code isn't a quick way to learn an API,
> and reading C# wrapped C source code is an even slower way!

Heh, I would not be too concerned about this.  The API looks pretty
simple, I have placed a tarball here:

	http://primates.ximian.com/~miguel/tmp/camel-index.tar.gz

> If it really does get adopted for monodoc, would there be any chance of
> you convincing the relevant person to write a high level overview of the
> library's architecture and/or key code points?

Yes, I think this can be done.  I just happened to be familiar, because
its the new and improved search engine (with a scalable incremental
updating facility, which might turn out to be important if we allow
pluggable documentation to be introduced).  This is the second
generation of text searching that was written for Evolution, and the
design was driven by the requirements exposed by Evolution with large
inboxes with large histories. 

> Is there any time frame/deadline on the browser's search development? If
> you think it might be worth it, I may take a look into how much work a
> Lucene based search feature would take?

No timeframe at this point.  As soon as I can get my hands on it, but I
have a lot on my queue right now.

Miguel.