SoC application idea proposal

David,

I don't represent the MonoDevelop team in any way, but
Google has
stated many times that Summer of Code projects should be
about
producing code.  Although I (and many others!) would love to
see the
MonoDevelop documentation improved, if I understand your
project
correctly, it is unlikely to be accepted by Google.

What plugins do you need?  Do you think they would benefit
others?
Perhaps one of them falls under the scope of a three month
coding
project?

Best of luck,
Sandy

On 3/15/07, David Anes <david.anesgmail.com> wrote:
> Hello all.
>
> I've been working with MonoDevelop for two years now as
my main Development
> Tool under Unix. I want to propose an Idea and submit
it to the Mono guys
> for metoring.
>
> The idea is to revamp all documentation as possible of
MonoDevelop:
> - document the sources a much as possible
> - put pages on the wiki explaining MD internal
architecture (althought Lluis
> has done some work on it).
> - integrate documentation into MonoDoc
>
> If you find that this could be useful, and given that I
want to learn the MD
> internals to hack on it and create some plugins that I
need and have as
> standalone applications, I could work on documenting
while learning.
>
> Is it a good idea? Or I move on to another one?
>
> Thank you all,
> David Anes.
>
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-listlists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
>
>
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

On 3/15/07, David Anes <david.anesgmail.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.

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

-- 
Michael Hutchinson
http://mjhutchinson.com
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

On 3/15/07, David Anes <david.anesgmail.com> wrote:
> Hi Sandford,
>
> 2007/3/15, Sanford Armstrong < sanfordarmstronggmail.com>:
> > David,
> >
> > I don't represent the MonoDevelop team in any way,
but Google has
> > stated many times that Summer of Code projects
should be about
> > producing code.  Although I (and many others!)
would love to see the
> > MonoDevelop documentation improved, if I
understand your project
> > correctly, it is unlikely to be accepted by
Google.
>
> 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...

Fortunately, you can make many proposals to increase your
chances.
  I'm
sure you saw the Mono ideas page (includes MonoDevelop
ideas):

http://ww
w.mono-project.com/StudentProjects

> > What plugins do you need?  Do you think they would
benefit others?
> > Perhaps one of them falls under the scope of a
three month coding
> > project?
>
> 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 would be great!  Good luck.

Sandy
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

On Thursday 15 March 2007 13:44:15 Michael Hutchinson
wrote:
> On 3/15/07, David Anes <david.anesgmail.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.


_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

El dj 15 de 03 del 2007 a les 16:17 +0100, en/na David Anes
va escriure:
> Hi Adam.
> 
> 2007/3/15, Adam Wood <AdamWoodxephi.co.uk>:
>         On Thursday 15 March 2007 13:44:15 Michael
Hutchinson wrote:
>         > On 3/15/07, David Anes <david.anesgmail.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.
> 
> What exactly do you mean?
> a) parse the code and generate docs (like Doxygen, NDoc
and many other
> do) 
> b) extract automatic documentation from assemblies
(annotated classes
> using attributes, using Reflection to retrieve class
heriarchies and
> so on).

Monodoc can already do all this. The monodocer tool can use
reflection
to parse an assembly and build documentation pages from it,
or it can
read documentation generated using the /doc command and also
generate
doc pages. Monodoc can then be used to edit the
documentation.

What would be nice to have is a better integration of all
this in
MonoDevelop. So for example, there would be a new
Documentation Project
that could be added to a solution and would automatically
generate and
keep track of documentation for projects.

Lluis.


_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st