Hello Jann!
As soon as the 8u40 repos open, the Accessibility code will be put back
along with the recent fixes for JAWS. Since OpenJFX (and the JDK) does
not have nightly builds, unless you want to wait for an EA build of 8u40
or 9, you will need to get OpenJFX and build it. This is really
This essentially matches my current thinking, however, I would have
DialogBox as an abstract superclass of Alert. Further, I would not have
many different types of show() methods.
Want to take the discussion further in the JIRA? That way, is will
track everyone's thinking on the various
In the past few days I've tested how well FX supports international
keyboard layouts. I've tested EN, DE, FR, RU, and JP keyboard layouts.
Note that myself, I only speak EN and RU, so I might have missed some
uncommon (or even some common) cases when trying to enter characters in
other
I agree that the four showXXX() methods are a slight complexity, but I think
they are simpler than the alternative. They quickly communicate the implied
Type of the DialogBox and response:
// Type Message: No response
DialogBox dbox = new DialogBox(FYI); dbox.setMessage(Just
Unfortunately there's nothing new and no Oracle sessions on that subject -
javafx on ios and/or android...
:(
--
Pedro Duque Vieira
Ok, let us know how you get on with building FX.
NOTE: The accessibility code is not there in 8u20 so you will just be
ensuring that you can build on Windows (there is nothing there to
test). The accessibility code will be going back into 8u40 on Monday or
Tuesday so you'll need to get that
Kevin, Daniel, Lisa,
Jira: https://javafx-jira.kenai.com/browse/RT-37594
From the jira:
Review at http://cr.openjdk.java.net/~ddhill/RT-37594/
http://cr.openjdk.java.net/%7Eddhill/RT-37594/
As part of this change we have:
* added an includeMonocle toggle (with a default of false)
* when
To be clear, you will still use the 8u-dev repo at the existing URL:
http://hg.openjdk.java.net/openjfx/8u-dev/rt
It's just that after Monday the repo will become the place where 8u40
work is done.
Regarding the build, it is a bit painful to set up for Windows, but not
too bad as long as
Don't expect anything from Oracle related to IOS and Android other than
some code contributions. They have said
ADF Mobile / Jdeveloper (etc) will suffer financially if Oracle supports
IOS and Android directly.
On Fri, Jun 20, 2014 at 9:43 AM, Pedro Duque Vieira
pedro.duquevie...@gmail.com
I hope you have similar success with the Windows build.
-- Kevin
Jann Schneider wrote:
Hi all,
The build instructions for linux where very good! I was able to build
the project without any problems.
Regards Jann
2014-06-20 19:27 GMT+02:00, Kevin Rushforth kevin.rushfo...@oracle.com:
To
Being non-Unix, Windows is always a pain.
Steve
On 2014-06-20, 3:42 PM, Kevin Rushforth wrote:
I hope you have similar success with the Windows build.
-- Kevin
Jann Schneider wrote:
Hi all,
The build instructions for linux where very good! I was able to build
the project without any
Jeff, could you please post your comments in Jira so that we don't lose
them?
Thanks!
-- Jonathan
On 21/06/2014 3:59 a.m., Jeff Martin wrote:
I agree that the four showXXX() methods are a slight complexity, but I think they are
simpler than the alternative. They quickly communicate the
Hi,
Well on windows it's always a bit more difficult i guess :-)
After setting up my build environment as described on the wiki i first tried
$ gradle tasks
This works as expected! When running
$ gradle sdk
or just gradle without any target i get the following error:
FAILURE: Build failed with
You'll need to run under a Cygwin shell or paths will be wrong. Fingers
crossed ...
Steve
On 2014-06-20, 5:12 PM, Jann Schneider wrote:
Hi,
Well on windows it's always a bit more difficult i guess :-)
After setting up my build environment as described on the wiki i first tried
$ gradle tasks
Yes looks like i have an issue with looking up cl.exe.
This was the output when running with --stacktrace:
* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task
':fxpackager:buildJavaPackager'.
...
Caused by: org.gradle.api.GradleException: Could not call
As a reminder, only approved changes should be going in this week (with
the noted exceptions). These rules are in effect until Monday, June 23 @
1am, after which the repo is frozen for (in)sanity testing. It is likely
to remain frozen for a bit longer than usual this time, but should open
back
i build
with the VS 2010 express (as suggested at the wiki).
I think that Express only supports 32-bit builds, but I may be wrong.
Anyway, glad to hear you are able to build!
If you want to know when the accessibility sources are back in the repo,
you can look for the commit messages or
Let's be a little bit more positive here guys...
From the link I posted you can see that there is a ton of JavaFX content at
JavaOne this year which is a very. very good sign in itself.
And, as I said, both iOS and Android are mentioned with featured sessions.
This is *new* in the sense that
I just pushed a changeset to update the last modified year in the
copyright header to 2014 for all files modified this year without the
header being modified. There were 1154 such files. Since this was a
comment-only change (I verified it two different ways), I pushed it
without review.
Hi Jann,
That is great that you got to build JavaFX, it will make much easier to test
patches and fixes going forward.
That said, assuming that you downloaded jdk1.8.0_20 b19 or less, accessibility
should have worked.
What is the output of java -version ? Can you try Narrator ?
I’ll put the
20 matches
Mail list logo
