[Mono-winforms-list] Re: Windows Forms.
Simon Ask Ulsnes
simon@ulsnes.dk
Sun, 26 Jan 2003 20:50:13 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_000B_01C2C57C.85FAD4E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In my opinion (and I may have misunderstood something), Mono should have =
its
own native Windows.Forms library that uses the most appropriate toolkit
(Gtk# for GNOME and Qt# for KDE). It would make no sense to user Wine =
for
anything else than providing compatibility with programs that use native
Win32 DLL calls, as existing toolkits can provide all the needed
functionality. (as far as I know, that is)
I think it will be utterly possible to make some wrapper classes for =
Gtk#,
making programmers able to create forms and so on the same way it is =
done
with the Windows.Form from the .NET Framework.
The bottom line is, it would be clever to get started using the Gtk#
classes - compatibility details (Win32 calls and so on) can be added =
later.
In general, I miss some status information on the Windows.Forms - Where =
are
we? What are future plans?
Yours,
Simon Ask Ulsnes, Denmark
----- Original Message -----
From: "Miguel de Icaza" <miguel@ximian.com>
To: <mono-winforms-list@ximian.com>
Sent: Sunday, January 26, 2003 8:15 PM
Subject: [Mono-winforms-list] Windows Forms.
> Hey guys,
>
> So we have a problem with Windows.Forms right now. To =
test/develop
> on Linux we need to get Wine to include support for a few semaphore =
API
> calls.
>
> As said before, Winforms implemented with Wine is required to have
> full support for Wndprocs and P/Invokes, and is the right way of doing
> things.
>
> The other option that we have scratched is to build Windows.Forms
> using a native toolkit, because we would not be able to achieve 100%
> compatibility.
>
> Idea: it would be useful to have a Windows.Forms implementation =
that
> used Gtk# at least to port existing Open Source Winforms code that we
> could tweak or ifdef chunks of code.
>
> Opinions?
>
> Miguel
>
>
> _______________________________________________
> Mono-winforms-list maillist - Mono-winforms-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-winforms-list
------=_NextPart_000_000B_01C2C57C.85FAD4E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>In my opinion (and I may have misunderstood something), Mono should =
have=20
its<BR>own native Windows.Forms library that uses the most appropriate=20
toolkit<BR>(Gtk# for GNOME and Qt# for KDE). It would make no sense to =
user Wine=20
for<BR>anything else than providing compatibility with programs that use =
native<BR>Win32 DLL calls, as existing toolkits can provide all the=20
needed<BR>functionality. (as far as I know, that is)<BR>I think it will =
be=20
utterly possible to make some wrapper classes for Gtk#,<BR>making =
programmers=20
able to create forms and so on the same way it is done<BR>with the =
Windows.Form=20
from the .NET Framework.<BR><BR>The bottom line is, it would be clever =
to get=20
started using the Gtk#<BR>classes - compatibility details (Win32 calls =
and so=20
on) can be added later.<BR><BR>In general, I miss some status =
information on the=20
Windows.Forms - Where are<BR>we? What are future =
plans?<BR><BR>Yours,<BR>Simon=20
Ask Ulsnes, Denmark<BR><BR>----- Original Message -----<BR>From: "Miguel =
de=20
Icaza" <<A =
href=3D"mailto:miguel@ximian.com">miguel@ximian.com</A>><BR>To:=20
<<A=20
href=3D"mailto:mono-winforms-list@ximian.com">mono-winforms-list@ximian.c=
om</A>><BR>Sent:=20
Sunday, January 26, 2003 8:15 PM<BR>Subject: [Mono-winforms-list] =
Windows=20
Forms.<BR><BR><BR>> Hey guys,<BR>><BR>> =
So we=20
have a problem with Windows.Forms right now. To =
test/develop<BR>> on=20
Linux we need to get Wine to include support for a few semaphore =
API<BR>>=20
calls.<BR>><BR>> As said before, Winforms=20
implemented with Wine is required to have<BR>> full support for =
Wndprocs and=20
P/Invokes, and is the right way of doing<BR>>=20
things.<BR>><BR>> The other option that we =
have=20
scratched is to build Windows.Forms<BR>> using a native toolkit, =
because we=20
would not be able to achieve 100%<BR>>=20
compatibility.<BR>><BR>> Idea: it would be =
useful=20
to have a Windows.Forms implementation that<BR>> used Gtk# at least =
to port=20
existing Open Source Winforms code that we<BR>> could tweak or ifdef =
chunks=20
of code.<BR>><BR>> =
Opinions?<BR>><BR>>=20
Miguel<BR>><BR>><BR>>=20
_______________________________________________<BR>> =
Mono-winforms-list=20
maillist - <A=20
href=3D"mailto:Mono-winforms-list@lists.ximian.com">Mono-winforms-list@li=
sts.ximian.com</A><BR>>=20
<A=20
href=3D"http://lists.ximian.com/mailman/listinfo/mono-winforms-list">http=
://lists.ximian.com/mailman/listinfo/mono-winforms-list</A><BR></DIV></BO=
DY></HTML>
------=_NextPart_000_000B_01C2C57C.85FAD4E0--