Flush

svn path=/trunk/mono/; revision=8635

1 files changed, 17 insertions, 5 deletions

diff --git a/web/winforms b/web/winforms
index 70730a75cbd..5d162147132 100644
--- a/web/winforms
+++ b/web/winforms
@@ -4,11 +4,10 @@
 	Win32 API, we will be using <a
 	href="http://www.winehq.com">WineLib</a> on Unix systems to
 	emulate the Win32 API.
-	
-	Although the original plans were to use Gtk on X and Cocoa on
-	MacOS X, it would be very hard to emulate the event model in
-	which some Winforms applications depend, and it would be very
-	hard to implement the Wndproc method.  
+
+	This means that those who want to contribute to the effort can
+	develop and test classes today using Windows and P/Invoke
+	calls to Win32 and we will then just run the result on Unix. 
 
 	In terms of integrating visually with the desktop, we are
 	hoping to contribute to the Wine project an mechanism to make
@@ -29,6 +28,11 @@
 	subscribe to it by sending an email message to <a
 	href="mailto:mono-winforms-list-request@ximian.com:.com">mono-winforms-list-request@ximian.com</a>.
 
+	If you want to help, you can start by writing a control and
+	testing it with Windows today (or you can also try to build
+	the existing library on Linux, but this is a bit more
+	complicated).  
+
 	Please read the README document in the
 	System.Windows.Forms/WINElib directory for details about how
 	to build the Windows.Forms support for Mono.
@@ -103,3 +107,11 @@
 	can accept either libart-like rendering operations and
 	X11-like rendering operations.  This complicates matters, but
 	I am not sure.  Someone needs to investigate this.
+
+* Historical 
+	
+	Although the original plans were to use Gtk on X and Cocoa on
+	MacOS X, it would be very hard to emulate the event model in
+	which some Winforms applications depend, and it would be very
+	hard to implement the Wndproc method.  
+