Re: [abbot-users] requirements for 1.0?

[Timothy W. <tw...@oc...>]

On Jan 23, 2004, at 8:10 PM, Thomas L Roche wrote:

>
> > * testers/recorders for remaining components. =A0I'd like to have at
> > least basic coverage for the things that aren't yet implemented:
>
> > =A0 =A0 AWT: =A0List, Scrollbar/Pane, TextArea/Field
> > =A0 =A0Swing: JColorChooser, JFileChooser, JOptionPane, =
JScrollbar/Pane,
> > [JSplitPane], JTableHeader, JToolBar
>
> Yeah, I gotta check on how complete we are on SWT also, given the
> constraint of
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D38436
>
>

(bug report regarding lack of location information for some widgets)

Remember that getting the component location is secondary to *driving*=20=

the component.  You only need the location if you have no other method=20=

of driving the component.  Ideally you'd have an exported action which=20=

sets the component state and notifies listeners, such that invoking the=20=

action is identical to mouse or key input (ignoring standard event=20
handling for the widget, which is assumed to be covered in the unit=20
testing of the widget itself).

AWT menus have no location information, but can be driven through the=20
accessibility layer or by posting actions on their behalf to the AWT=20
event queue.  Same is true for certain other AWT components.