Lesson plan
Form (programming)
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.
Article summary
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.
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.