[Mono-list] Windows forms

[Kaloian Doganov]

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

I disagree.

First, the Java Abstract Windowing Toolkit (AWT) has no its own Look and
Feel. Widows AWT implementation uses native Win32 widgets, and
Unix/Linux AWT implementation uses Motif.

Second, Swing provides Pluggable Look&Feel mechanism -- there are
platform-independend Java Look&Feel (hated by you, I see ;-)), but also
Windows Look&Feel and Motif Look&Feel. Under MacOS X, there is also
another Aqua look&feel. For example, see how jEdit runs under MacOS X:

http://www.jedit.org/index.php?page=3Dscreenshots

There are also thid-pary look&feels for Swing, listed at:

http://www.javootoo.com

It's true, of course, that we don't see a lot of Java implementation on
the client side. But the Look&Feel issue is not the reason for that.


=CD=E0 =EF=ED, 2002-07-08 =E2 12:58, Douglas and Elena Husemann =E7=E0=EF=
=E8=F1=E0:
> The Swing UI is half the reason you don't see alot of java implementation=
 on the
> client side.
> It doesn't have the look and feel of the client.

> But I do know from the little I have played with Java that most of the us=
ers
> hated the programs generated
> with it using the "universal" gui because it did not have the feel of Win=
dows,
> or Amiga, or Mac depending
> on which user you talked to.


--=-7pPUwpiqM8HfL5qiNoNx
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)

iD8DBQA9KgnUbgjhpf5UubQRAn6lAKDTgdOxxpdbXz9L3Tpn+hKhSJm1nwCeInEM
PTnvuDRP/45LBf1QB7dOyXI=
=KTpK
-----END PGP SIGNATURE-----

--=-7pPUwpiqM8HfL5qiNoNx--