[Mono-winforms-list] Vote?
Dan Maltes
dan@astusa.com
Tue, 28 Jan 2003 11:16:32 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_0002_01C2C6BE.B7059F00
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
If a vote is done, I just hope folks rally around the decision and make
a united effort to get it done, and that those who didn't get what they
voted for don't decide to go another direction and resources end up
getting too fractured. That would only slooooow things down. As much
as I would like to not see a bloated, buggy winelib swf, in the end it's
probably the only way to get the highest swf portability.
-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: Tuesday, January 28, 2003 11:01 AM
To: mono-winforms-list@ximian.com
Subject: [Mono-winforms-list] Vote?
Seems we're stuck with too many different opinions as to how the SWF
implementation on Mono should be written... May I suggest that someone
set up a voting system so random visitors on www.go-mono.com can tell ud
their opinion? I think this would be a good solution since it is people
who are going to use Mono in the end who are most interested in the
project and visits the site more often. A note could be sent to OSNews
about it, or something...
I was thinking that choices could be:
1. Pure Gtk#
2. Pure Qt#
3. Both (using the most appropriate for each system - this will take A
LOT of coding to do...)
4. WineLib implementation, providing full Win32 API support (if
possible).
Then we could measure "common people"'s opinions and take them into
consideration... Right now there seems to be an equal amount of
arguments for this and that, and I really feel we need to do something
soon - this is very frustrating :-)
I don't think it will matter much if we will have to make som huge
changes to the code that might come out of it at a later point, as long
as something is being done.
Yours sincerely,
Simon Ask Ulsnes, Denmark
------=_NextPart_000_0002_01C2C6BE.B7059F00
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=3D648301216-28012003><FONT face=3DArial color=3D#0000ff =
size=3D2>If a=20
vote is done, I just hope folks rally around the decision and make a =
united=20
effort to get it done, and that those who didn't get what they voted for =
don't decide to go another direction and resources end up =
getting too=20
fractured. That would only slooooow things down. As much as =
I would=20
like to not see a bloated, buggy winelib swf, in the end it's probably =
the only=20
way to get the highest swf portability.</FONT></SPAN></DIV>
<DIV><SPAN class=3D648301216-28012003><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D648301216-28012003><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> Tuesday, January 28, 2003 11:01 =
AM<BR><B>To:</B>=20
mono-winforms-list@ximian.com<BR><B>Subject:</B> [Mono-winforms-list]=20
Vote?<BR><BR></FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>Seems we're stuck with too many =
different=20
opinions as to how the SWF implementation on Mono should be written... =
May I=20
suggest that someone set up a voting system so random visitors on <A=20
href=3D"http://www.go-mono.com">www.go-mono.com</A> can tell ud their =
opinion? I=20
think this would be a good solution since it is people who are going =
to use=20
Mono in the end who are most interested in the project and visits the =
site=20
more often. A note could be sent to OSNews about it, or=20
something...</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2></FONT> </DIV>
<DIV><FONT face=3DTahoma size=3D2>I was thinking that choices could=20
be:</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>1. Pure Gtk#</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>2. Pure Qt#</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>3. Both (using the most appropriate =
for each=20
system - this will take A LOT of coding to do...)</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>4. WineLib implementation, providing =
full Win32=20
API support (if possible).</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2></FONT> </DIV>
<DIV><FONT face=3DTahoma size=3D2>Then we could measure "common =
people"'s opinions=20
and take them into consideration... Right now there seems to be an =
equal=20
amount of arguments for this and that, and I really feel we need to do =
something soon - this is very frustrating :-)</FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2>I don't think it will matter much if =
we will=20
have to make som huge changes to the code that might come out of it at =
a later=20
point, as long as something is being done.</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_0002_01C2C6BE.B7059F00--