Button behaviors (look clicked, press-and hold), also select-lists, etc. - Consider them systematically to be an input selection method. So they go here! *** These are not widgets why? Because they are tied directly to the input method. A spinner is not used on a pure scroll-and-select device, because it's solving the input problem of touch only. Right??? NEED BETTER NAME!!!!

Forms as a way to collect information in an ordered manner pre-date computing by at least a century. Many standards were developed in the paper form era, and have translated to computerized database forms, and then to web forms. The ubiquity of the web -- to software developers if not all users -- means forms for all computing types have settled on these standard input methods.

WEBFORM SUMMARY (from wikipedia): text – a simple text box that allows input of a single line of text (an alternative, password, is used for security purposes, in which the characters typed in are invisible or replaced by symbols such as *) checkbox – a check box radio – a radio button file – a file select control for uploading a file reset – a reset button that, when activated, tells the browser to restore the values to their initial values. submit – a button that tells the browser to take action on the form (typically to send it to a server) textarea – much like the text input field except a textarea allows for multiple rows of data to be shown and entered select – a drop-down list that displays a list of items a user can select from

Note that we're not gonna define radio and check, as they don't vary much from their web or database variants. while patterns in the sense that they are widgets to be used, there's not enough variation to include here.

Oh, and Submit buttons are covered under the Button pattern. Reset is an anti-pattern at best. Maybe even remove from the list...