From jhill at arcfocus.com  Sun May 11 10:26:46 2008
From: jhill at arcfocus.com (jhill)
Date: Sun, 11 May 2008 07:26:46 -0700 (PDT)
Subject: [Mono-docs-list]  Testing Nabble - Please Ignore
Message-ID: <17170562.post@talk.nabble.com>


Nothing to see here.  Sorry for the noise.

--Joseph
-- 
View this message in context: http://www.nabble.com/Testing-Nabble---Please-Ignore-tp17170562p17170562.html
Sent from the Mono - Documentation mailing list archive at Nabble.com.


From miguel at novell.com  Fri May 30 19:53:41 2008
From: miguel at novell.com (Miguel de Icaza)
Date: Fri, 30 May 2008 19:53:41 -0400
Subject: [Mono-docs-list] The future of monodoc.dll
In-Reply-To: <1206193675.21631.14.camel@lina.magi.jprl.com>
References: <1206193675.21631.14.camel@lina.magi.jprl.com>
Message-ID: <1212191621.6334.91.camel@frost>

Hello,

> One of the things I'd like to do before the Mono 2.0 release is migrate
> monodoc.dll to use C# 2.0 features such as generics in the public API.
> For example, instead of Monodoc.Node.Nodes being an ArrayList, it should
> be an IEnumerable<Node> or IList<Node>, and Monodoc.Node should
> implement IComparable<Node>, etc.
> 
> However, I'm not sure that this can actually be done, as monodoc.dll is
> installed into the GAC, and such an API change would break any existing
> clients on upgrade.

We can consider monodoc.dll in the GAC as being an internal API, it was
never supposed to be an API set in stone, we never really advertised it,
and other than MonoDevelop, I do not believe there are many users of it.

So I would not sweat too much about it.

> 4. Something else?

This one ;-)

Its an internal API, lets just move ahead.

> Thoughts?
>  - Jon
> 
> 
> _______________________________________________
> Mono-docs-list maillist  -  Mono-docs-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-docs-list

From miguel at novell.com  Fri May 30 19:54:42 2008
From: miguel at novell.com (Miguel de Icaza)
Date: Fri, 30 May 2008 19:54:42 -0400
Subject: [Mono-docs-list] The future of monodoc.dll
In-Reply-To: <ef36f55f0803221118jdc66dc8y8528bf664b4fafe@mail.gmail.com>
References: <1206193675.21631.14.camel@lina.magi.jprl.com>
	<1206203959.22193.21.camel@t61p.site>
	<ef36f55f0803221118jdc66dc8y8528bf664b4fafe@mail.gmail.com>
Message-ID: <1212191682.6334.94.camel@frost>


> * no easy way of installing new documentation (or updated one)

Yes, there is an easy way.   Drop in the new files.

The only thing we have not made is easy is to modify the tree, but that
was done on purpose, so we would get third-parties always under
"various".

We can revisit this decision if its important.