FocusTraversalPolicy is very general mechanism that allows to define any
kinds of traversal sequences.

However, it is not very easy to do - user needs to create its own policy
and somehow define the order there. One of the most common uses of FTP
is to define order by providing the rule: which component is next after
which. If for every component such rule is defined, the sequences is
complete. Very often such policies are created, the rule is defined by
putting all components into the array which defines the order - after
the component with index i, the next component is the one with index
i+1.

Such policies represent the most common use case for FTP.

Previously, it was possible to define such policies using the API in
JComponent, setNextFocusableComponent. It seems that current API, using
FTP, is much harder to use than JComponent - one needs to track all
components, and manage additional structure with information that is
related to JComponent.

As the solution to this problem, the easier way to define FTPs presented
above should be provided. It must be either FTP that allows to specify
the order between components without creating new FTP descendant each
time(by using array or by methods similar to setNextFocusableComponent),
or the API in JComponent must be undeprecated, and FTP that uses this
information directly must be created.
###@###.### 2004-08-19
###@###.### 2004-08-19