[Gtk-sharp-list] Re: [Mono-devel-list] A larger patch for the monodoc-browser
Miguel de Icaza
miguel at ximian.com
Wed May 21 10:42:50 EDT 2003
> Would I be right in thinking that this is purely the "index feature",
> (as in a book index), and that work on "indexing" for the search feature
> hasn't yet started? Or are you planning to reuse the same backend for
> both features?
This is purely an index/table-of-contents feature. The search engine
should use its own body-text indexing.
> A few posts recently are all very ambiguous (without staring at a fair
> bit of code) as to which indexing they mean. It appears as if all recent
> indexing discussion is to do with creating the index feature, rather
> than creating an indexer API for the providers to use to populate data
> for the search feature.
It has both currently: the populating API is there, and the code to
write it out to disk is there.
This is only used to implement the panel on the left in this screenshot:
> Miguel, do you think it would be appropriate to add a line/subsection to
> each item in browser/TODO with details of who, if anyone, is working on
> each feature?
Yes, that makes sense.
> Again, I'm a little confused as to whether this means there's now an API
> for providers to add data to a search index?
There is an API for adding data to the table-of-contents index.
More information about the Mono-devel-list