[MonoDevelop] ideas

Asier Llano Palacios asier@bips78.bi.ehu.es
Thu, 15 Jan 2004 08:07:51 +0100

My thoughts.

1) Of course. It would be hard to compete in windows with SharpDevelop
itself, just because it uses native toolkits, and I think it would be
useless. Maybe it would be a lot smarter to keep the work in sync with
SharpDevelop, so that it is MonoDevelop for Linux and SharpDevelop for
Windows, sharing 95% of the code, and using 5% of specific code for the
specific platform. It should be great if the work of the SharpDevelop and
MonoDevelop work is synchronized, even if there is some code that is
different. (What about having only one repository, with some common code
multiplatform, some code Windows specific, and some code Linux specific to
avoid the synchronization work?). It would be a pity if both projects
diverge enough so that the work is always done twice, the combines of one
project cannot be used in the other one, the plugins cannot be shared, etc.

2) Monodoc is great, and I'm sure it even will improve, because there are
skillful people on it. The integration with it seems good enough.


-----Mensaje original-----
De: monodevelop-list-admin@lists.ximian.com
[mailto:monodevelop-list-admin@lists.ximian.com] En nombre de Todd Berman
Enviado el: jueves, 15 de enero de 2004 1:44
Para: monodevelop-list@lists.ximian.com
Asunto: [MonoDevelop] ideas

Ok, now that you guys have had access to the sources a bit, im going to
start posting here general development stuff to see if we can get a bit
of a discussion going.

1) I know that originally I has said we would be maintaining Windows
compatability at all times, but having since thought about this, is
there really a point? Windows already has VS.NET and the original #D,
why would this be something that people feel is useful?

Would it be better in the long term to use Gnome and all sorts of linux
things to enhance MonoDevelop?

For example, printing should really use gnome-print on linux, it is
already wrapped and working under C#, why reinvent that wheel, or any
number of wheels we will have to end up reinventing to stay working on

2) What should we use for a help format. Obviously .chm will not work on
linux easily :) Would tying into monodoc be the best thing to do using
it's xhtml provider? or would it be better to use devhelp or something

These are just a couple thoughts I had on the wonderful ttc ride home
from work, I'm sure you all have plenty as well, so lets figure this
type of stuff out.

Keep in mind, we are accepting patches for MonoDevelop, so if you
download the sources and want to contribute, just send a svn diff to
this list, or potentially file a bug if its a bugfix.

Happy Hacking


Monodevelop-list mailing list