Assuming your test program is in the unnamed module (meaning it is run
from a jar file or directory of classes on the classpath), the following
will work:
java -XaddExports:javafx.graphics/com.sun.glass.ui=ALL-UNNAMED
-- Kevin
Benjamin Gudehus wrote:
>And we will certainly need to use thi
>And we will certainly need to use this for our own unit testing, too.
Details are tbd, but you will be able to use it for testing.
Anything new about the command line switch to access Robot? :)
--Benjamin
enjfx-dev@openjdk.java.net"
Date:08/07/2015 05:51 AM
Subject: Re: Results of review of private JavaFX API for
consideration to make public in JDK 9
Sent by:"openjfx-dev"
--
Hi Jonathan,
thanks for the summary!
pull
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 logistic
>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
ch
> in Java 9 that would grant TestFX access to internals?
>
>
> Neil
>
>
>
>
> From:Benjamin Gudehus
> To:jonathan.gi...@oracle.com,
> Cc:"openjfx-dev@openjdk.java.net"
> Date: 08/07/2015 05:51 AM
> Su
Thanks, I will ! :-)
Sent from my iPad
> On 11 août 2015, at 00:33, Jonathan Giles wrote:
>
> It is likely that these classes will be included as part of JEP 253 (in
> subproject 3), so they will likely become public API. Javadoc output for this
> subproject will be posted in the next week or
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 Pul
It is likely that these classes will be included as part of JEP 253 (in
subproject 3), so they will likely become public API. Javadoc output for
this subproject will be posted in the next week or two. Keep your eyes
peeled :-)
-- Jonathan
On 11/08/2015 4:42 a.m., Hervé girod wrote:
It passed
It passed under my radar that we use classes in com.sun.javafx.css, and
com.sun.javafx.css.parser, mainly :
- CSSParser
- Stylesheet
- Selector
- Rule
The use case is to be able to process JavaFX stylesheets properties.
Hervé
Sent from my iPad
> On 7 août 2015, at 01:10, Jonathan Giles wrote:
If there were to be an API for getting basic graphics device data, what
would that look like and would it be hard to write?
My app uses some internal APIs not listed above to query the pixel scale
and whether we're using software/hardware graphics, to reduce usage of some
expensive effects. These
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).
>These classes a
12 matches
Mail list logo
