Web Development

Web application framework whose architecture is based on the Model-View-Controller pattern in which requests are routed through a controller that provides overall application management and dispatches the requests to application components

A standard component API for specifying the state and behavior of a wide range of components, including simple components, such as input fields, and more complex components, such as scrollable data tables.

Also create components based on these APIs, and many third parties have already done so and have made their component rendering model that defines how to render the components in various ways. For example, a component used for selecting an item from a list can be rendered as a menu or a set of radio buttons.

An event and listener model that defines how to handle events generated by activating a component, such as what to do when a user clicks a button. Conversion and validation models for converting and validating component data.