Talk:Windows Forms

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
???	This article has not yet received a rating on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.

Microsoft Windows: Computing Unassessed

	This article is within the scope of WikiProject Microsoft Windows, a collaborative effort to improve the coverage of Microsoft Windows on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Microsoft WindowsWikipedia:WikiProject Microsoft WindowsTemplate:WikiProject Microsoft WindowsMicrosoft Windows
???	This article has not yet received a rating on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Computing.

This article is a sad, sad little stub. Can anybody flesh out some extra information? See the article on MFC for an idea.

The MdiContainer Property of a Windows Form seems to be very similar to the Document/View architecture of MFC. I think the note to the contrary is wrong.

Some comments after reading (except the obvious small size):

The MVC comment is a bit strange. If you look at the MVC page, only webapps have strict V-C separations, and for that we have ASP.NET. All other application widget set roughly treat it the same as Winforms.
Vista part, and connection to WPF. Is WPF a sucessor, competing technology? Will Winforms become (slow) GDI+?

Is this a correct explanation for the Swing-link?

"Swing, the equivalent GUI application programming interface (API) for the Java programming language"

I think, from a programming point of view, it might be correct, but technically, it's something completely different (since WinForms is native and Swing is drawing everything by itself).

Merger proposal (controls)

BackgroundWorker and RichTextBox are two .NET components that strangely have their own articles. These should just be made into a list as part of an article covering a larger subject. While RichTextBox definitely fits in the Windows Forms article (along with other controls), as a part of System.Windows.Forms, BackgroundWoker is actually a part of System.ComponentModel, but may fit in this article nonetheless. Both of those namespaces are listed in Base Class Library, and a quickly located list of some controls (as an example) is here: [1]. --David Gannon (talk) 05:36, 6 December 2007 (UTC)[reply]