Talk:Windows Forms

From Wikipedia, the free encyclopedia

	This article is part of WikiProject Microsoft Windows, a WikiProject devoted to maintaining and improving the informative value and quality of Wikipedia's many Microsoft Windows articles.
Stub	This article has been rated as stub-Class on the assessment scale.
Mid	This article has been rated as mid-importance on WikiProject Microsoft Windows's importance scale.

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).

[edit] 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)

If there is no discussion, I will perform the mergers I find necessary and expand this into an appropriate article. --David Gannon (talk) 06:07, 6 December 2007 (UTC)

I consent your proposal, and propose that Windows Forms application be merged into the Windows Forms article. QQ (talk) 18:57, 13 January 2008 (UTC)

Windows Forms and Windows Forms Application are two different things in this context. The first one refers to the .NET API and the second one to a application type (opposed to console applications). Da Stranger - 27 February 2008.

While may technically refer to windows in Windows Forms Applications, I think merging Windows Forms application, Windows Forms, Windows Forms component and BackgroundWorker together make tons of sense and should be done ASAP, with the other articles deleted. We can clarify the App vs. Window nuance in the article. We probably should compare WinForm App with WPF app. Christopher G Lewis (talk) 19:16, 1 March 2008 (UTC)