Peter Dennis Bartok
Sun, 27 Feb 2005 15:53:32 -0700
The code doesn't have to be complete to be documented. The APIs are well
From: "Dasnois Benjamin" <firstname.lastname@example.org>
To: "Miguel de Icaza" <email@example.com>
Cc: "James Pickering" <TiggerJimLinux@hotmail.com>; "winforms"
Date: Sunday, 27 February, 2005 14:43
Subject: Re: [Mono-winforms-list] Documentation
>sorry to bring back this post 7 days after the last message but I
>think that at the time when Peter said me I should stop working on MWF
>implementation he told me to work on the documentation. I can't see
>any problem at working on the doc although the implementation is not
>complete as it begins to be usable and will be the final way of
>implementing winforms. Also I've seen that most API are not documented
>in monodoc and I hope that it will not be the case of MWF.
>On Sun, 20 Feb 2005 13:45:33 -0500, Miguel de Icaza <firstname.lastname@example.org>
>> > Just a small question. Is their any documentation for monodoc or raw
>> > documentation which can be imported into monodoc?
>> > I know this is all work in progress, but I would like to start using
>> > MWF for projects. The only reason I ask is that I can not use the
>> > on-line MSDN since do not have a "always on" Internet connection.
>> > Sorry to bother everybody
>> The solution to do this would be to run the monodocer program, but I
>> recommend that we only check into SVN documentation stubs for classes
>> that are API complete today.
>> Mono-winforms-list maillist - Monoemail@example.com
>Mono-winforms-list maillist - Monofirstname.lastname@example.org