[Mono-devel-list] porting SharpDevelop

Rob.Tillie at Student.tUL.EDU Rob.Tillie at Student.tUL.EDU
Mon Jul 5 15:07:39 EDT 2004

Comments inline.

> -----Original Message-----
> From: Pascal Deliot [mailto:pascal at deliot.com]
> Im a little disapointed by your anwer!
> I thought that the main interest of the CLI is the inter-platform
> compatibility.
> Then in the theory if you have an'ECMA-compatible runtime engine (and the
> MCS base calsses) you should run the same "binary" on all platform.

System.Windows.Forms is not (yet) part of the ECMA standard. I favor in
getting one widget toolkit (available in both MS.NET and Mono) to be
standardized with ECMA / ISO, hopefully the Longhorn widget toolkit...

> If you must write a version by OS and compile one CLI for each one, why
> don't use C++ language and GCC?

Because C++ is inherently slower programming then an IL-based language,
because it is lower-level and doesn't have a class library.

> I've made some tests with simples GUI programs running pretty well with
> mono. And i hope the future will allow us to maintain only one source code
> and one CLI for all platform.

We're getting close :)

-- Rob.

> -----Message d'origine-----
> De : mono-devel-list-admin at lists.ximian.com [mailto:mono-devel-list-
> admin at lists.ximian.com] De la part de Steve Deobald
> Envoyé : lundi 5 juillet 2004 03:35
> À : Carter Smithhart
> Cc : mono-devel-list at lists.ximian.com
> Objet : Re: [Mono-devel-list] porting SharpDevelop
> On Sun, 2004-07-04 at 18:21, Carter Smithhart wrote:
> > > You have heard about monodevelop (website:
> > > http://www.monodevelop.com) right?
> > >
> > > --Todd
> >
> > Yeah.. I played around with it for a bit.. It doesn't have a GUI
> > builder embedded within yet, so I thought I'd look around for another
> way.
> > Another reason I looked elsewhere is because I was looking for a GUI
> > builder that generates code using the System.Windows.Forms namespace.
> > I guess I also wanted some experience with what "porting" a C# app
> > would be like.
> Ha ha! Interesting way to go about it, I guess. :)
> You might want to have a look at mono's System.Windows.Forms (SWF)
> implementation before you try to make this journey. It's actually broken
> at the moment, and the process of re-writing it has just recently begun.
> The other thing you may want to look at is GTK#. It would probably require
> less effort to port any SWF app to GTK# (as the MonoDevelop team has done
> with SharpDevelop) than trying to piece together broken pieces of SWF. I
> would recommend finding a much smaller SWF app, and porting that to GTK#
> to familiarize yourself with the API. Then, if you're looking for features
> in MonoDevelop which haven't been added yet, perhaps you could give the
> team a hand? :) The amount they've accomplished in MonoDevelop's short
> lifespan is almost unfathomable:
> teams at various companies are already using MonoDevelop for enterprise
> application development, which speaks volumes about the work done so far.
> I think it's a project worth contributing to.
> --
> Steve Deobald
> Software Architect
> www.citygroup.ca
> www.cityhost.ca
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

More information about the Mono-devel-list mailing list