https://github.com/testfx/robot
A test bed for a public API of JavaFX's robot classes.
https://github.com/testfx/robot
Last synced: about 1 year ago
JSON representation
A test bed for a public API of JavaFX's robot classes.
- Host: GitHub
- URL: https://github.com/testfx/robot
- Owner: TestFX
- License: gpl-2.0
- Created: 2015-12-14T09:19:15.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2015-12-14T15:56:45.000Z (over 10 years ago)
- Last Synced: 2025-05-14T02:42:23.379Z (about 1 year ago)
- Language: Java
- Homepage:
- Size: 62.5 KB
- Stars: 1
- Watchers: 2
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
## OpenJFX/Robot
This is a test bed for a public API of JavaFX's robot classes. These classes are for purposes of
test automation, self running demos and other applications where control of the mouse and keyboard
is needed.
**Note:** This API is unstable and subject to change. The code is currently intended
for JDK `1.8.0_65`, this will change to JDK `1.9` eventually.
### Candidates
Glass robot:
- `com.sun.glass.ui.Robot`
- `com.sun.glass.ui.Pixels`
- `com.sun.glass.ui.Application::createRobot()`
- `com.sun.glass.ui.Application::createPixels()`
Scene robot:
- `com.sun.javafx.robot.FXRobot`
- `com.sun.javafx.robot.FXRobotFactory`
- `com.sun.javafx.robot.FXRobotImage`
### Ideas
- The robots should be placed into `javafx.robot`?
- The robots should be named `InputRobot` (`com.sun.glass`) and `EventRobot` (`com.sun.javafx`)?
- Use a separate class for `Image` data and pixel `Buffer`s?
- Robot interfaces should match `FXRobot` as close as possible?
- Use `int`s for coordinates and dimensions?
- Add flag for wait-for-idle functionality?
- Factory methods in `javafx.application.Application` or separate factory classes?
### License
OpenJDK and OpenJFX are licensed under the [GNU General Public License, version 2, with the
Classpath Exception][GPL2+CE].
[GPL2+CE]: http://openjdk.java.net/legal/gplv2+ce.html