[Mono-devel-list] Re: A larger patch for the monodoc-browser

Philip Van Hoof spamfrommailing at freax.org
Tue May 20 18:14:13 EDT 2003


On Tue, 2003-05-20 at 23:23, Miguel de Icaza wrote:

> What is the difference between "Select all" and "Copy"?
> I am not sure I like the idea of having "View/Expand All", that is
> likely a very time consuming process.  I would be ok with "View/Expand
> all children" though.

Indeed, it needs some time to Expand All nodes. It is, however, only
necessary to do this once. It's not easy to do this in a worker-thread
(when using gtk-sharp). This way the "Expand All" could be made as a
background process. 
[CUT]

>  So this would just be a temporary solution.

Agree 
> As for the Index: I have checked in my code for creating an index, but
> it is not completed yet.  The new indexing code principle is that each
> provider would "populate" the table of contents with information that
> people would look for.   Once the data is populated, a compact index
is
> written out.  Then this is used to present a list that the user can
> browser, or can be used to dynamically search the index. 
> Very much like the Microsoft help  browser for the .NET framework.

Sounds like an excellent idea to me

> Now, the shortcomings (and you are free to get involved here):
> 
>       * The providers are not populating all the data they should,
>         currently they are only doing this for the proof-of-concept,
>         bootstrap phase.
> 
>       * There is no compression of text.  And there is quite a lot of
>         redundancy, so index files are very large.
>       
>       * I have not written the widget to display this information.
> 
>         Since the index might contain millions of rows, it is not
>         possible to load the information in memory, nor use the
>         standard "Gtk.TreeModel" stores, because it would just consume
>         too much memory to just display.
>         Few options:
> 
>               * Create a wrapper that would allow C# code to implement
>                 the tree models with managed code, without having
>                 to "populate" them.
> 
>               * Create a new list-widget (not hard to do, but would be
>                 a duplication of effort) for browsing it.
> So could you rework your patch a bit to cope with this?
> You did a great job.  I wonder if I can get you interested on taking
on
> some of the other pieces missing in Monodoc (there is a "NOTES" file
in
> monodoc/browser with various pending items).

Okay,

I have to warn you about my free time that is going to get reduced in a
few days :). I have both a new job and exams coming up within two weeks.
ps. Thats why I gave myself two weeks off (which I am filling with
reading the sources of Mono at this moment -- My new job will be about
.NET and OpenSource, so it wont hurt --)



-- 
Philip Van Hoof a.k.a. freax
me at freax dot org
http://www.freax.be -- http://www.freax.eu.org -- http://www.freax.org





More information about the Mono-devel-list mailing list