Windows Forms is the name accustomed to the graphical appliance programming interface (API) included as a allotment of Microsoft .NET Framework, accouterment admission to built-in Microsoft Windows interface elements by wrapping the actual Windows API in managed code. While it is apparent as a backup for the beforehand and added circuitous C++ based Microsoft Foundation Class Library, it does not action a archetype commensurable to Model–View–Controller. Some after-market and third affair libraries accept been created to accommodate this functionality. The best broadly acclimated of these is the User Interface Process Appliance Block, which is appear by the Microsoft patterns & practices accumulation as a chargeless download that includes the antecedent cipher for quick alpha examples.
Friday, 12 August 2011
History & future
Just like Abstract Window Toolkit (AWT), the agnate Java API, Windows Forms was an aboriginal and accessible way to accommodate graphical user interface apparatus to the .NET Framework. Windows Forms is congenital on the actual Windows API and some controls alone blanket basal Windows components[1]
Windows Forms provides a cross-platform way to architecture graphical user interfaces. However WinForms is mainly a adhesive about the Windows API, and some of the methods acquiesce absolute admission to Win2 callbacks, which are not accessible in added platforms than Windows[1].
Windows Forms has been in aftereffect abolished by Windows Presentation Foundation (and its associated GUI allegorical accent alleged XAML). Since WPF is almost new, it is cryptic if Windows Forms will abide to be bigger in approaching .NET releases
Windows Forms provides a cross-platform way to architecture graphical user interfaces. However WinForms is mainly a adhesive about the Windows API, and some of the methods acquiesce absolute admission to Win2 callbacks, which are not accessible in added platforms than Windows[1].
Windows Forms has been in aftereffect abolished by Windows Presentation Foundation (and its associated GUI allegorical accent alleged XAML). Since WPF is almost new, it is cryptic if Windows Forms will abide to be bigger in approaching .NET releases
Architecture
A Windows Forms appliance is an event-driven appliance accurate by Microsoft's .NET Framework. Unlike a accumulation program, it spends best of its time artlessly cat-and-mouse for the user to do something, such as ample in a argument box or bang a button.
Alternative implementation
Mono is a activity led by Xamarin (formerly by Ximian, again Novell) to actualize an Ecma accepted adjustable .NET accordant set of tools.
Mono's abutment for System.Windows.Forms as of .NET 2.0 is appear as complete[5] ; additionally System.Windows.Forms 2.0 works natively on Mac OS X[6]. However, Windows.Forms is not actively developed on Mono[7], and abounding affinity with .NET is not accomplished and is not possible, because WinForms is mainly a adhesive about the Windows API, and some of the methods acquiesce absolute admission to Win2 callbacks, which are not accessible in added platforms than Windows
Mono's abutment for System.Windows.Forms as of .NET 2.0 is appear as complete[5] ; additionally System.Windows.Forms 2.0 works natively on Mac OS X[6]. However, Windows.Forms is not actively developed on Mono[7], and abounding affinity with .NET is not accomplished and is not possible, because WinForms is mainly a adhesive about the Windows API, and some of the methods acquiesce absolute admission to Win2 callbacks, which are not accessible in added platforms than Windows
Subscribe to:
Posts (Atom)