[Mono-winforms-list] Windows Forms is crucial for the future success

Peter Custance PCustance@tokairo.com
Mon, 26 Jul 2004 09:13:11 +0100


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C472E8.648678D0
Content-Type: text/plain

Mono - Views from a Windows developer.

 

Ok, first some history. I have been a Windows developer for 10 years
starting with the C programming language. I then moved into VB at version 4
before progressing to VB.Net and finally to C#. During that time period I
have watched the rise of the various Linux distros with interest. I have
played around with many of them and I am a strong advocator of choice. I
have even tried the various Linux based toolkits such as Tcl, Qt and Gtk. So
I was very interested when I discovered the Mono Project. I have followed
Mono now for over a year and have ported much of my Dot Net Assemblies over
into Linux. Now comes the rub, Windows Forms. Now most programmers are
creatures of habit and like to stick with what they know and feel
comfortable with and yes I know Windows Forms is only a preview in the
latest version of Mono. 

 

I get the general feeling that those in the Linux community would like to
see us use the Gtk# toolkit and Monodevelop does not have a Windows Form
Project type. I have to say that for most of us that would mean supporting
two sets of GUI code. I can tell you right now, it will not happen.
Developers simply do not have the time to do this so Windows Forms are
crucial to the future of Mono if it wants to be a serious cross-platform
toolkit. I personally think that using Wine to do this is wrong and the
Windows Forms classes should map to native code but that is just my opinion.


 

At the end of the day if the Mono community and Linux as a whole is to
benefit from this project and expect to see many programs ported across to
Linux they must implement Windows Forms or many windows developers
anticipating an easy way to port their applications will lose interest fast.
I for one have put a few projects on hold at this point. I have tried the
preview version of Windows Forms and it cannot even successfully show a
message box without going screwy.

 

So to the mono programmers I say don't let us down on this most important
part of the project and I am sure this will be a great success. I for one
would like all my future products to work on Windows and Linux.

 

Peter Custance


------_=_NextPart_001_01C472E8.648678D0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">


<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Mono - Views from a Windows =
developer.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Ok, first some history. I have been a Windows =
developer for
10 years starting with the C programming language. I then moved into VB =
at
version 4 before progressing to VB.Net and finally to C#. During that =
time
period I have watched the rise of the various Linux distros with =
interest. I
have played around with many of them and I am a strong advocator of =
choice. I
have even tried the various Linux based toolkits such as Tcl, Qt and =
Gtk. So I
was very interested when I discovered the Mono Project. I have followed =
Mono
now for over a year and have ported much of my Dot Net Assemblies over =
into
Linux. Now comes the rub, Windows Forms. Now most programmers are =
creatures of
habit and like to stick with what they know and feel comfortable with =
and yes I
know Windows Forms is only a preview in the latest version of Mono. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I get the general feeling that those in the Linux =
community
would like to see us use the Gtk# toolkit and Monodevelop does not have =
a
Windows Form Project type. I have to say that for most of us that would =
mean
supporting two sets of GUI code. I can tell you right now, it will not =
happen.
Developers simply do not have the time to do this so Windows Forms are =
crucial
to the future of Mono if it wants to be a serious cross-platform =
toolkit. I
personally think that using Wine to do this is wrong and the Windows =
Forms
classes should map to native code but that is just my opinion. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>At the end of the day if the Mono community and =
Linux as a
whole is to benefit from this project and expect to see many programs =
ported
across to Linux they must implement Windows Forms or many windows =
developers
anticipating an easy way to port their applications will lose interest =
fast. I
for one have put a few projects on hold at this point. I have tried the =
preview
version of Windows Forms and it cannot even successfully show a message =
box
without going screwy.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>So to the mono programmers I say don't let us down =
on this
most important part of the project and I am sure this will be a great =
success.
I for one would like all my future products to work on Windows and =
Linux.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Peter Custance<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C472E8.648678D0--