[Mono-list] Windows.Forms, KDE

[Matej Spiller]

Is there really need to do this with conditionally code? Its ugly, and Gtk#
is more developed than other (they are actually not at all yet). So its hard
to maintain when you have 4 widgets sets.  I mean why not create completly
separate dlls, that have same dll name (system.windows.forms.dll) and when
you compile you select diferent dll, you wish to compile and then use.

Or even create one dll, that dinamicaly calls others widgets dlls. So you
have one Windows.Forms.dll and it delegates calls to others dlls. For
example you have Windows.Forms.dll, Windows.Forms.Qt.dll,
Windows.Forms.Gtk.dll Windows.Forms.Orig.dll.. On windows you simply replace
Windwos.Forms.dll with new one and woila you can have even under windows as
many widgets as you wish. Without changing the code.
And then you have one utlity where you can set your prefered widgets.

Matej Spiller
----- Original Message -----
From: "Miguel de Icaza" <miguel@ximian.com>
To: "Adam Treat" <manyoso@yahoo.com>
Cc: "Paolo Molaro" <lupus@ximian.com>; "Mono-list" <Mono-list@ximian.com>
Sent: Thursday, July 04, 2002 10:06 PM
Subject: Re: [Mono-list] Windows.Forms, KDE


> > BTW, when Qt# is ready I wonder whether the Windows.Forms wrapper should
be
> > created in Mono's cvs or somewhere else?  Mono's cvs would centralize
the
> > work, but this would require a dependancy on Qt# (which in turn requires
qtc
> > ;-) which is in kde's cvs at the moment.
>
> We can always conditionally compile the code, so the dependency will be
> optional.
>
> But see my other mail about my position on Windows.Forms at this point.
>
> Miguel
>
> _______________________________________________
> Mono-list maillist  -  Mono-list@ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>