 | This article does not cite any sources. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Form" programming – news · newspapers · books · scholar · JSTOR (December 2009) (Learn how and when to remove this message) |
In component-based programming (Visual Basic, .NET WinForms, Gambas, Delphi, Lazarus etc.), a form is a representation of a GUI window. A form contains components and controls, typically including "OK" and "Cancel" buttons; these objects provide a high-level abstraction of standard or custom widgets which are typically much easier to manipulate than the GUI's underlying API.
At design time, visual controls (buttons, text boxes, and the like) and non-visual components (timers, database connections, layout aids, and so on) are placed on the form. These controls and components are positioned and sized interactively, and their properties and event handlers are set with a special editor typically laid out as a grid.
At runtime, automatically generated code creates instances of these controls and components, and sets their properties.
Historically, forms were often implemented as screens on a block-oriented terminal connected to a mainframe computer. HTML forms are conceptually very similar.
See also
- Form (document)
- Form (HTML)
- FormEngine
- Master-detail
- Oracle Forms
- Windows Forms
- Windows_Presentation_Foundation
- Xamarin.Forms
- XForms
 | This programming-language-related article is a stub. You can help Misplaced Pages by expanding it. |