| Package | Description |
|---|---|
| com.codename1.cloud |
Provides cloud related services such as storage, binding widgets to the cloud seamlessly so they can be persisted
easily.
|
| com.codename1.components |
Generic elaborate components that make use of both UI elements and storage.
|
| com.codename1.contacts |
Provides access to the contacts list from the device address book
|
| com.codename1.facebook |
Legacy generic implementation of the Facebook API with simplified OAuth integration to allow social sharing.
|
| com.codename1.io.services |
Default WebService implementations
|
| com.codename1.ui |
Main widget package containing the component/container "composite" similar
both in terminology and design to Swing/AWT.
|
| com.codename1.ui.list |
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, notice that we strongly
discourage usage of lists...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. |
| com.codename1.ui.plaf |
Look of the application can be fully customized via this package, it represents
a rendering layer that can be plugged in separately in runtime and themed to
provide any custom look.
|
| com.codename1.ui.spinner |
Spinners allows picking of simple sequential values similarly to combo boxes but of a much wider value set.
|
| com.codename1.ui.util |
Utility features that are either too domain specific or don't "fit" into any
other packages including the Resource file format loading API.
|
| Class and Description |
|---|
| ListModel
Represents the data structure of the list, thus allowing a list to
represent any potential data source by referencing different implementations of this
interface, notice that
we strongly
discourage usage of lists..
|
| Class and Description |
|---|
| ListModel
Represents the data structure of the list, thus allowing a list to
represent any potential data source by referencing different implementations of this
interface, notice that
we strongly
discourage usage of lists..
|
| MultipleSelectionListModel
Events
ListModel to support multiple selection. |
| Class and Description |
|---|
| DefaultListModel
Default implementation of the list model based on a
List of elements. |
| ListModel
Represents the data structure of the list, thus allowing a list to
represent any potential data source by referencing different implementations of this
interface, notice that
we strongly
discourage usage of lists..
|
| MultipleSelectionListModel
Events
ListModel to support multiple selection. |
| Class and Description |
|---|
| DefaultListModel
Default implementation of the list model based on a
List of elements. |
| Class and Description |
|---|
| ListModel
Represents the data structure of the list, thus allowing a list to
represent any potential data source by referencing different implementations of this
interface, notice that
we strongly
discourage usage of lists..
|
| Class and Description |
|---|
| ListCellRenderer
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
Represents the data structure of the list, thus allowing a list to
represent any potential data source by referencing different implementations of this
interface, notice that
we strongly
discourage usage of lists..
|
| Class and Description |
|---|
| CellRenderer
Deprecated.
this interface was added for ContainerList which is now deprecated. Use GenericListCellRenderer
or ListCellRenderer instead
|
| ContainerList
Deprecated.
the performance of ContainerList is worse than the performance of List or Container. The API/behaviors
are problematic and we don't think its the right choice for any project. It is our recommendation that you use
Container, InfiniteContainer etc.
|
| ListCellRenderer
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
Represents the data structure of the list, thus allowing a list to
represent any potential data source by referencing different implementations of this
interface, notice that
we strongly
discourage usage of lists..
|
| MultipleSelectionListModel
Events
ListModel to support multiple selection. |
| Class and Description |
|---|
| ListCellRenderer
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.
|
| Class and Description |
|---|
| ListCellRenderer
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
Represents the data structure of the list, thus allowing a list to
represent any potential data source by referencing different implementations of this
interface, notice that
we strongly
discourage usage of lists..
|
| Class and Description |
|---|
| ContainerList
Deprecated.
the performance of ContainerList is worse than the performance of List or Container. The API/behaviors
are problematic and we don't think its the right choice for any project. It is our recommendation that you use
Container, InfiniteContainer etc.
|
Copyright © 2021. All rights reserved.