[Mono-winforms-list] A few beginner questions
Kevin Rector
krector@compco.com
Tue, 14 Sep 2004 08:49:39 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_001B_01C49A37.C54CF3D0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Hello, is there a list anywhere of what's being worked on in the new
implementation and what needs to be worked on?
Also, I'm assuming that classes should be implemented to copy the MS
version. Is there a particular reason why we use the exact same namespaces
as Microsoft? The reason I ask is that I would think it would be helpful to
have the mono classes in a namespace other than System.Windows.Forms so that
I could include a Mono version and a Microsoft version on the same form to
compare behaviors. Perhaps there is a good reason and I just don't see it.
Thanks,
Kevin Rector
------=_NextPart_000_001B_01C49A37.C54CF3D0
Content-Type: text/html;
charset="us-ascii"
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:0in;
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:"Courier New";
color:navy;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>Hello, =
is there a
list anywhere of what’s being worked on in the new implementation =
and
what needs to be worked on?<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>Also, =
I’m
assuming that classes should be implemented to copy the MS version. Is =
there a
particular reason why we use the exact same namespaces as Microsoft? The =
reason
I ask is that I would think it would be helpful to have the mono classes =
in a
namespace other than System.Windows.Forms so that I could include a Mono
version and a Microsoft version on the same form to compare behaviors. =
Perhaps
there is a good reason and I just don’t see =
it.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'>Thanks,<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Courier =
New"><span
style=3D'font-size:10.0pt;font-family:"Courier New";color:navy'>Kevin =
Rector<o:p></o:p></span></font></p>
</div>
</body>
</html>
------=_NextPart_000_001B_01C49A37.C54CF3D0--