Anyone can create a bug here:
http://bugs.java.com/
No, it isn't the same as having direct access to JIRA, but the bugs will
end up in the same bug database.
-- Kevin
Benjamin Gudehus wrote:
It would be good to discuss this via a JBS issue. Please file one and we
can discuss logistics further.
I have no project author status on JBS to create an issue. :/ I could sign
the Oracle Contributor Agreement, but I doubt I will able provide the two
required non-trivial patches anytime soon in order to become an author.
This was much easier with the previous OpenJFX issue system.
On Tue, Aug 11, 2015 at 12:36 AM, Jonathan Giles <jonathan.gi...@oracle.com>
wrote:
On 7/08/2015 9:51 p.m., Benjamin Gudehus wrote:
Hi Jonathan,
thanks for the summary!
pull up your sleeves and work with us to get the API into a shape where
it is good enough to commit to as public API
I'd like to help with the public API for profiling and performance
tracking (mainly PulseLogger, maybe PerformanceTracker).
It would be good to discuss this via a JBS issue. Please file one and we
can discuss logistics further.
These classes are com.sun.javafx.util.Utils,
com.sun.javafx.PlatformUtil, and com.sun.javafx.application.PlatformImpl.
As most of these classes are just a collection of self-contained methods,
it is quite likely that a number of these methods will find public API
alternatives in a new class
Sounds good. TestFX has a dependency to
com.sun.javafx.application.ParametersImpl to provide the ability to test
multiple different `Application`s. It currently depends on private fields
and methods of internal classes.
It is highly unlikely that ParemetersImpl will be made public API.
Robot: A good API to make public, but not a small API, so the scope is
possibly too great for JDK 9.
The headless testing feature in TestFX has dependencies to
com.sun.javafx.robot.FXRobot and com.sun.glass.ui.Robot. As TestFX uses the
AWT robot, the "normal" testing mode needs no access to the internal APIs.
The screenshot feature in headless testing depends on
com.sun.javafx.robot.FXRobotImage and com.sun.glass.ui.Pixels.
Additionally we also need access to com.sun.glass.ui.PlatformFactory in
order to activate Monocle on desktop systems.
These areas are outside my area of expertise, but my understanding is that
it is extremely unlikely that any of the classes you mentioned will become
public API in JDK 9.
-- Jonathan
