[MonoDevelop] Fwd: SoC application idea proposal

[David Anes]

2007/3/15, Michael Hutchinson <m.j.hutchinson at gmail.com>:
>
> 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.


Ok, then let's think on other type of projects.

> 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.


Well,  a class Designer  is a good one. I like it.

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.


About the canvas there is no problem. I've been working for two years now in
a diagramming engine (closed source still) to represent any kind of diagram
(we are working now with BPMN, Goal Models, Flow and UML diagrams). I will
be happy creating a new diagramming framework using Cairo and Gtk, and a
plugin for MonoDevelop.

--
> Michael Hutchinson
> http://mjhutchinson.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/monodevelop-list/attachments/20070315/51b59379/attachment.html