[Mono-list] Windows forms

Kaloian Doganov kaloian@bgit.net
09 Jul 2002 00:51:04 +0300


--=-3FIRq1KwLfVDYTfREIgb
Content-Type: text/plain; charset=Windows-1251
Content-Transfer-Encoding: quoted-printable

Here is quite different point of view:

The incompatibility between Windows-based toolkit (Windows.Forms) and
GNU/Linux based one (Gtk#) is a Good Thing!

Why?

Because this will force the cross-platform aimed programmers to
architect clean Model-View-Controller (MVC) programs. IMHO, the main
task for Mono here is to provide a way to write cross-language and
cross-platform libraries. If you code your application's core as an
engine, then later you can write different frontends to it -- a
Windows.Forms one and a Gtk# one.

This is the only way to make all Windows, GNOME, Qt, Tk, Motif, etc.
guys happy. And IMHO:

1. Your need to write your application twice to support different
toolkits implies that your app is already a mess.

2. Just using Mono or Microsoft .NET will not be enough to render your
programs cross-platform.

3. Of course, this will not let us use VB.NET's Wizards generated apps
on our wonderful GNU/Linux boxes, but I think I can live with that. ;-)


Best regards,
Kaloian.

=CD=E0 =EF=ED, 2002-07-08 =E2 12:27, code =E7=E0=EF=E8=F1=E0:

> The key point is cross-platform. If a toolkit can only run under in
> Linux or Windows, I will not use it. I don't want to write program
> twice.=20


--=-3FIRq1KwLfVDYTfREIgb
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA9KglIbgjhpf5UubQRAgyPAJ9frvhgvbbyuFPhDwwC98ctbHWWvgCfSZPI
e/AJ0/LMBF/nrggoNmRNQg0=
=wAHT
-----END PGP SIGNATURE-----

--=-3FIRq1KwLfVDYTfREIgb--