[Mono-winforms-list] Let me get this right...
Dan Maltes
dan@astusa.com
Mon, 27 Jan 2003 11:03:50 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_0006_01C2C5F3.C69762D0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
I agree with Simon, why force Wine to have to be used for winform apps
that may never really need "true" win32 emulation? Why force the
overhead?? Somehow, make it optional for winform apps that require
wndproc and p/invoke to use wine winforms, but have gtk# available as
the default. I know, easiar said than done, and trust me I wish I was a
systems programmer so I could help out, but I'm only an applications
developer.
-Dan
-----Original Message-----
From: mono-winforms-list-admin@lists.ximian.com
[mailto:mono-winforms-list-admin@lists.ximian.com] On Behalf Of Simon
Ask Ulsnes
Sent: Monday, January 27, 2003 10:17 AM
To: mono-winforms-list@ximian.com
Subject: [Mono-winforms-list] Let me get this right...
Those arguing that Mono should use WineLib in the SWF implementation, do
they mean that to create a basic windows with controls on it Mono should
be interacting with the Mono libraries? Because that makes absolutely no
sense to me. (If it does, please explain why)
1. That would require every Mono/Linux desktop user to install Wine as
well to execute almost every CLR-program that he will come across.
2. It would require a lot of cooperation with the Wine devteam, which I
am sure have enough to do.
3. It would be such a waste of the Gtk# and Qt# implementations, since
noone will use them because then they will lose cross-platform
compatibility. When they're there, let's use them! I don't think it
requires many resources to write two SWF libraries on top of Gtk# and
Qt# respectively. (I would be happy to contribute in this, but it would
require me to get a lot more involved in how both Gtk and Qt works)
Basically, all the functionality has already been written (well, a lot
of it - Gtk# is at version 0.7!).
As far as the Gtk+2 layout issues are concerned, I don't think that will
be a very big problem.
Yours sincerely,
Simon Ask Ulsnes, Denmark
------=_NextPart_000_0006_01C2C5F3.C69762D0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D994255815-27012003><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
agree with Simon, why force Wine to have to be used for winform apps =
that may=20
never really need "true" win32 emulation? Why force the=20
overhead?? Somehow, make it optional for winform apps that require =
wndproc=20
and p/invoke to use wine winforms, but have gtk# available as =
the=20
default. I know, easiar said than done, and trust me I wish I was =
a=20
systems programmer so I could help out, but I'm only an applications=20
developer.</FONT></SPAN></DIV>
<DIV><SPAN class=3D994255815-27012003><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D994255815-27012003><FONT face=3DArial color=3D#0000ff =
size=3D2>-Dan</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
mono-winforms-list-admin@lists.ximian.com=20
[mailto:mono-winforms-list-admin@lists.ximian.com] <B>On Behalf Of =
</B>Simon=20
Ask Ulsnes<BR><B>Sent:</B> Monday, January 27, 2003 10:17 =
AM<BR><B>To:</B>=20
mono-winforms-list@ximian.com<BR><B>Subject:</B> [Mono-winforms-list] =
Let me=20
get this right...<BR><BR></FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>Those arguing that Mono should use =
WineLib in=20
the SWF implementation, do they mean that to create a basic windows =
with=20
controls on it Mono should be interacting with the Mono libraries? =
Because=20
that makes absolutely no sense to me. (If it does, please explain=20
why)</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>1. That would require every =
Mono/Linux desktop=20
user to install Wine as well to execute almost every CLR-program that =
he will=20
come across.</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>2. It would require a lot of =
cooperation with=20
the Wine devteam, which I am sure have enough to do.</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>3. It would be such a waste of the =
Gtk# and Qt#=20
implementations, since noone will use them because then they will lose =
cross-platform compatibility. When they're there, let's use them! I =
don't=20
think it requires many resources to write two SWF libraries on top of =
Gtk# and=20
Qt# respectively. (I would be happy to contribute in this, but it =
would=20
require me to get a lot more involved in how both Gtk and Qt works) =
Basically,=20
all the functionality has already been written (well, a lot of it - =
Gtk# is at=20
version 0.7!).</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2></FONT> </DIV>
<DIV><FONT face=3DTahoma size=3D2>As far as the Gtk+2 layout =
issues are=20
concerned, I don't think that will be a very big problem.</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2></FONT> </DIV>
<DIV><FONT face=3DTahoma size=3D2>Yours sincerely,<BR>Simon Ask =
Ulsnes,=20
Denmark</FONT></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0006_01C2C5F3.C69762D0--