[MonoDevelop] Fwd: SoC application idea proposal

Adam Wood AdamWood at xephi.co.uk
Thu Mar 15 10:07:39 EDT 2007

On Thursday 15 March 2007 13:44:15 Michael Hutchinson wrote:
> On 3/15/07, David Anes <david.anes at gmail.com> wrote:
> > Ok, I've always proposed  projects  that "produce code" to the SoC, but
> > this time I wanted to do someting different. I will try to propose still
> > for Mono mentoring anyway, maybe there is a chance...
> The question is not whether we would accept it -- IIRC Google has
> explicitly said that they won't accept projects for creating
> documentation. That said, you could work on documentation-related
> code, such as improving MonoDoc or its integration with MonoDevelop.

How about a MonoDevelop plugin for automatically generating documentation and 
UML representations from code? You could use the MonoDevelop sources as your 
test case and maybe do something like adding attributes to the code for 
inserting extra documentation. Surely this fulfils the need for a code based 
project that allows you to learn the internals of MonoDevelop whilst also 
helping EVERYONE out by creating some good documentation and letting them do 
the same for their own apps.

I'm thinking of something along the lines of the DOxygen system.

> > I'm interested in plugins to extract info about class heriarchies, to
> > draw "sexy" class diagrams that could be printed. That way, we could
> > create enhanced documentations of our personal/work projects. I think a
> > "View class hieriachy as UML" plugin could be nice. I will propose this
> > one also.
> That's a really good idea. Have you seen the VS2005 Class Designer
> surface? It's absolutely wonderful for designing class hierarchies and
> object oriented structures, or visualising or modifying existing ones.
> SharpDevelop has recently added something like this too, which you can
> look at. IMHO actual UML might be a bit too formal.
> MonoDevelop's existing refactoring capabilities should be up to the
> task -- the difficult thing is the canvas. It would be nice if it
> could share code with a future database designer surface.

More information about the Monodevelop-list mailing list