Every Infusion application is structured as a set of "components". An Infusion component can represent a visible component on screen, a collection of related functionality such as an "object" as in object-orientation, or simply a unit of work or relationship between other components. This page provides resources to help you understand components, how they're designed and how to work with them.
If you're creating an entire web application, your application would be implemented as a component that coordinates interactions between other components that handle the different parts of your application.
To help understand how a widget or application might be designed using components, consider some of the components in the Infusion Component Library:
The Inline Edit component allows user to edit text in place, without switching to a new screen, by simply switching into an in-place edit mode. The view mode is implemented one way, with certain functionality (i.e. a tooltip, an affordance to edit), and the edit mode is implemented differently: it's an edit field. Conceptually, these two modes are rather different, and so they're implemented as two separate subcomponents of the main Inline Edit component.
What Does A Component Look Like?
Most will have:
Depending on what the component is for, some will include infrastructure to support
New kinds of components are created by passing configuration information to the