ComboBox
and
other components (such as carousels etc) they employ a similar MVC approach to
Swing including the renderer pattern.See: Description
Interface | Description |
---|---|
CellRenderer<T> |
This class is geared to replace the ListCellRenderer in the long run to provide a more
generic rendering API.
|
ListCellRenderer<T> |
A "rubber stamp" tool that allows us to extract a component (often the same
component instance for all invocations) that is initialized to the value
of the current item extracted from the model, this component is drawn on the
list and discarded.
|
ListModel<T> |
Represents the data structure of the list, thus allowing a list to
represent any potential data source by referencing different implementations of this
interface.
|
Class | Description |
---|---|
ContainerList |
This is a "list component" implemented as a container with a layout manager
which provides some of the ui advantages of a Container and some of a
list while pulling out some of the drawbacks of both.
|
DefaultListCellRenderer<T> |
Default implementation of the renderer based on a label see the
ListCellRenderer
for more information about the use and purpose of this class |
DefaultListModel<T> |
Default implementation of the list model based on a vector of elements
|
FilterProxyListModel<T> |
This class allows filtering/sorting a list model dynamically using a text field
|
GenericListCellRenderer<T> |
The generic list cell renderer can display containers or arbitrary Codename One components
as items in a list.
|
MultiList |
A list with a multi-button renderer by default
|
Lists are highly customizable and serve as the basis for ComboBox
and
other components (such as carousels etc) they employ a similar MVC approach to
Swing including the renderer pattern. ListCellRenderer
allows us to customize the appearance of a list entry, it works as a
"rubber stamp" by drawing the rendered component and discarding its state thus
allowing very large lists with very little component state overhead.
ListModel
allows us to represent the underlying
data structure for the List
/ComboBox
without requiring all the data to reside in memory or in a specific structure.
This allows a model to represent a data source of any type, coupled with the renderer the
data source can be returned in an internal representation state and still be rendered
properly to the screen.