Re: Testing accessibility / sample apps

[Felipe Heidrich]

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 code back early next week, either Monday or Tuesday.
You can track the progress here: https://javafx-jira.kenai.com/browse/RT-37536
I’ll email the list when the code is out.

Regards,
Felipe



On Jun 20, 2014, at 4:00 PM, Jann Schneider  
wrote:

> ok i just rebuild using the 32 bit jdk and this works!
> $ gradle clean sdk
> ...
> BUILD SUCCESSFUL
> 
> :-)
> 
> I think i've just installed the 32 bit C++ compilers only. Maybe i
> missed a setting in the installer of visual studio .. btw. i build
> with the VS 2010 express (as suggested at the wiki).
> 
> So i'll wait until the accessibility portion is back in the repo and
> try with that included then. Thanks for your help so fahr!
> @Steve: could you please send a short message to the list if the
> accessibility sources are in the repo again?
> 
> 
> Regards
> Jann
> 
> 
> 2014-06-20 23:50 GMT+02:00, Jann Schneider :
>> 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
>> NativeCompileTask.compile() on task ':fxpackager:buildJavaPackager'
>> ...
>> Caused by: java.util.concurrent.ExecutionException:
>> org.gradle.process.internal.ExecException: A problem occurred starting
>> process 'command 'C:/Program Files (x86)/Microsoft Visual Studio
>> 10.0/VC/BIN/amd64/cl.exe''
>> ...
>> Caused by: java.io.IOException: Cannot run program "C:/Program Files
>> (x86)/Microsoft Visual Studio 10.0/VC/BIN/amd64/cl.exe" (in directory
>> "D:\jann\sandbox\java\openjfx\modules\fxpackager"): CreateProcess
>> error=2, Das System kann die angegebene Datei nicht finden
>> ...
>> Caused by: java.io.IOException: CreateProcess error=2, Das System kann
>> die angegebene Datei nicht finden (file not found)
>> 
>> Actually cl.exe is located at: C:\Program Files (x86)\Microsoft Visual
>> Studio 10.0\VC\bin - but it looks for ...bin/amd64/cl.exe
>> 
>> I've also tried to run the build from the cygwin terminal and as well
>> from the visual studio command prompt where i could call cl.exe
>> directly .. Always the same result.
>> 
>> Is there a parameter to specify where theVS compiler and stuff is
>> located? btw. i checked that the %VS100COMNTools% variable is set
>> properly.
>> 
>> What else could i check? Thanks in advance :)
>> 
>> Jann
>> 
>> 
>> 
>> 
>> 2014-06-20 23:30 GMT+02:00, Kevin Rushforth :
>>> 
 * What went wrong:
 Execution failed for task ':fxpackager:buildJavaPackager'.
 
 Could not call NativeCompileTask.compile() on task
 ':fxpackager:buildJavaPackager'
>>> 
>>> When I've seen this in the past it's been related to the compiler
>>> install. Do you have VS 2010 SP1 or something else?
>>> 
>>> -- Kevin
>>> 
>>> 
>>> 
>>> 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
 This works as expected! When running
 $ gradle sdk
 or just gradle without any target i get the following error:
 
 FAILURE: Build failed with an exception.
 
 * What went wrong:
 Execution failed for task ':fxpackager:buildJavaPackager'.
 
> Could not call NativeCompileTask.compile() on task
> ':fxpackager:buildJavaPackager'
> 
 
 Is this a "known issue" and do you know what's going wrong here?
 Should i post more "info" or "debug" output, too?
 
 Thanks
 Jann
 
 
 
 2014-06-20 21:58 GMT+02:00, Stephen F Northover
 :
 
> 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 problems.
>>> 
>>> Regards Jann
>>> 
>>> 2014-06-20 19:27 GMT+02:00, Kevin Rushforth
>>> :
>>> 
 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 you don't need to build WebKit. We would be
 interest

Copyright year update [was: hg: openjfx/8u-dev/rt: RT-37588: Update copyright header for files modified in 2014]

[Kevin Rushforth]

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. However, if anyone wants to take a look at the 
changeset, the URL is below.


As a reminder, when you do modify a file, please check the copyright 
year and update it if not already modified. It's easy to forget, though, 
so I'll likely do this again around the time of the 8u40 rampdown.


-- Kevin



Changeset: 65ed4256d047
Author:kcr
Date:  2014-06-20 17:09 -0700
URL:   http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/65ed4256d047

RT-37588: Update copyright header for files modified in 2014

...
  


Long list of files snipped.

Re: JavaFX at JavaOne 2014

[Felix Bembrick]

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 these sessions were not there last year
(even if they may have been announced and cancelled prior to the actual
event).

Orc course we all agree that JavaFX must run on iOS and Android for it to
be viable long-term but that's exactly what Johan and the wizards at RoboVM
are doing.  Sure, it's not *official* Oracle support yet but that will come.

For those who are not aware, when Sun first released Java, it did not run
on Linux.  One member from the community stepped-up, put the hours in and
used his brilliant brain to port Java to Linux and that this port was
subsequently officially adopted by Sun themselves.

That person was Johan so if anyone is going to be in charge of the JavaFX
to Android port then Johan is the best person I can think of.

Oracle themselves now are publicly throwing their support behind RoboVM and
Johan's ports and we all need to do the same.  As a community, we can make
these ports happen and then I am extremely confident that Oracle will
embrace them officially.

Felix




On 21 June 2014 07:31, Pedro Duque Vieira 
wrote:

> @Johan
> Hey Johan,
>
> Nothing new in the sense that I know your excellent work on the android
> port, by the way thank you very much for that, please keep it up :). And I
> also know the work on the ios side with RoboVM.
> -
>
> If it is correct that JavaFX won't be supporting iOS or Android
> (officially), IMO JavaFX will start fading away as soon as there is a
> reliable technology that can create apps for all platforms. Like for
> instance, improvements to HTML5 or other technologies that might arise.
> The user percentage of desktop users is dropping significantly in favor of
> mobile platforms.
>
>
>
> On Fri, Jun 20, 2014 at 8:04 PM, Johan Vos  wrote:
>
> > Hi Pedro,
> >
> > What makes you think there is nothing new?
> >
> > - Johan
> >
> >
> > 2014-06-20 18:43 GMT+02:00 Pedro Duque Vieira <
> pedro.duquevie...@gmail.com
> > >:
> >
> > Unfortunately there's nothing new and no Oracle sessions on that subject
> -
> >> javafx on ios and/or android...
> >>
> >> :(
> >>
> >> --
> >> Pedro Duque Vieira
> >>
> >
> >
>
>
> --
> Pedro Duque Vieira
>

Re: Testing accessibility / sample apps

[Kevin Rushforth]

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 watch JIRA issue 
https://javafx-jira.kenai.com/browse/RT-37536 (although I'm sure Steve 
or Felipe will send a message).


If you don't want to wait, you could apply Felipe's patch from that JIRA 
issue to your local build and try it yourself before then.


-- Kevin


Jann Schneider wrote:

ok i just rebuild using the 32 bit jdk and this works!
$ gradle clean sdk
...
BUILD SUCCESSFUL

:-)

I think i've just installed the 32 bit C++ compilers only. Maybe i
missed a setting in the installer of visual studio .. btw. i build
with the VS 2010 express (as suggested at the wiki).

So i'll wait until the accessibility portion is back in the repo and
try with that included then. Thanks for your help so fahr!
@Steve: could you please send a short message to the list if the
accessibility sources are in the repo again?


Regards
Jann


2014-06-20 23:50 GMT+02:00, Jann Schneider :
  

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
NativeCompileTask.compile() on task ':fxpackager:buildJavaPackager'
...
Caused by: java.util.concurrent.ExecutionException:
org.gradle.process.internal.ExecException: A problem occurred starting
process 'command 'C:/Program Files (x86)/Microsoft Visual Studio
10.0/VC/BIN/amd64/cl.exe''
...
Caused by: java.io.IOException: Cannot run program "C:/Program Files
(x86)/Microsoft Visual Studio 10.0/VC/BIN/amd64/cl.exe" (in directory
"D:\jann\sandbox\java\openjfx\modules\fxpackager"): CreateProcess
error=2, Das System kann die angegebene Datei nicht finden
...
Caused by: java.io.IOException: CreateProcess error=2, Das System kann
die angegebene Datei nicht finden (file not found)

Actually cl.exe is located at: C:\Program Files (x86)\Microsoft Visual
Studio 10.0\VC\bin - but it looks for ...bin/amd64/cl.exe

I've also tried to run the build from the cygwin terminal and as well
from the visual studio command prompt where i could call cl.exe
directly .. Always the same result.

Is there a parameter to specify where theVS compiler and stuff is
located? btw. i checked that the %VS100COMNTools% variable is set
properly.

What else could i check? Thanks in advance :)

Jann




2014-06-20 23:30 GMT+02:00, Kevin Rushforth :


* What went wrong:
Execution failed for task ':fxpackager:buildJavaPackager'.

Could not call NativeCompileTask.compile() on task
':fxpackager:buildJavaPackager'


When I've seen this in the past it's been related to the compiler
install. Do you have VS 2010 SP1 or something else?

-- Kevin



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
This works as expected! When running
$ gradle sdk
or just gradle without any target i get the following error:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':fxpackager:buildJavaPackager'.



Could not call NativeCompileTask.compile() on task
':fxpackager:buildJavaPackager'

  

Is this a "known issue" and do you know what's going wrong here?
Should i post more "info" or "debug" output, too?

Thanks
Jann



2014-06-20 21:58 GMT+02:00, Stephen F Northover
:



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 problems.

Regards Jann

2014-06-20 19:27 GMT+02:00, Kevin Rushforth
:

  

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 you don't need to build WebKit. We would be
interested in hearing whether the instructions on the Wiki are
sufficient for you to get the build working.

-- Kevin


Stephen F Northover wrote:



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 release at that time and
build
it instead when it becomes availabl

Re: Testing accessibility / sample apps

[Jann Schneider]

ok i just rebuild using the 32 bit jdk and this works!
$ gradle clean sdk
...
BUILD SUCCESSFUL

:-)

I think i've just installed the 32 bit C++ compilers only. Maybe i
missed a setting in the installer of visual studio .. btw. i build
with the VS 2010 express (as suggested at the wiki).

So i'll wait until the accessibility portion is back in the repo and
try with that included then. Thanks for your help so fahr!
@Steve: could you please send a short message to the list if the
accessibility sources are in the repo again?


Regards
Jann


2014-06-20 23:50 GMT+02:00, Jann Schneider :
> 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
> NativeCompileTask.compile() on task ':fxpackager:buildJavaPackager'
> ...
> Caused by: java.util.concurrent.ExecutionException:
> org.gradle.process.internal.ExecException: A problem occurred starting
> process 'command 'C:/Program Files (x86)/Microsoft Visual Studio
> 10.0/VC/BIN/amd64/cl.exe''
> ...
> Caused by: java.io.IOException: Cannot run program "C:/Program Files
> (x86)/Microsoft Visual Studio 10.0/VC/BIN/amd64/cl.exe" (in directory
> "D:\jann\sandbox\java\openjfx\modules\fxpackager"): CreateProcess
> error=2, Das System kann die angegebene Datei nicht finden
> ...
> Caused by: java.io.IOException: CreateProcess error=2, Das System kann
> die angegebene Datei nicht finden (file not found)
>
> Actually cl.exe is located at: C:\Program Files (x86)\Microsoft Visual
> Studio 10.0\VC\bin - but it looks for ...bin/amd64/cl.exe
>
> I've also tried to run the build from the cygwin terminal and as well
> from the visual studio command prompt where i could call cl.exe
> directly .. Always the same result.
>
> Is there a parameter to specify where theVS compiler and stuff is
> located? btw. i checked that the %VS100COMNTools% variable is set
> properly.
>
> What else could i check? Thanks in advance :)
>
> Jann
>
>
>
>
> 2014-06-20 23:30 GMT+02:00, Kevin Rushforth :
>>
>>> * What went wrong:
>>> Execution failed for task ':fxpackager:buildJavaPackager'.
>>>
>>> Could not call NativeCompileTask.compile() on task
>>> ':fxpackager:buildJavaPackager'
>>
>> When I've seen this in the past it's been related to the compiler
>> install. Do you have VS 2010 SP1 or something else?
>>
>> -- Kevin
>>
>>
>>
>> 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
>>> This works as expected! When running
>>> $ gradle sdk
>>> or just gradle without any target i get the following error:
>>>
>>> FAILURE: Build failed with an exception.
>>>
>>> * What went wrong:
>>> Execution failed for task ':fxpackager:buildJavaPackager'.
>>>
 Could not call NativeCompileTask.compile() on task
 ':fxpackager:buildJavaPackager'

>>>
>>> Is this a "known issue" and do you know what's going wrong here?
>>> Should i post more "info" or "debug" output, too?
>>>
>>> Thanks
>>> Jann
>>>
>>>
>>>
>>> 2014-06-20 21:58 GMT+02:00, Stephen F Northover
>>> :
>>>
 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 problems.
>>
>> Regards Jann
>>
>> 2014-06-20 19:27 GMT+02:00, Kevin Rushforth
>> :
>>
>>> 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 you don't need to build WebKit. We would be
>>> interested in hearing whether the instructions on the Wiki are
>>> sufficient for you to get the build working.
>>>
>>> -- Kevin
>>>
>>>
>>> Stephen F Northover wrote:
>>>
 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 release at that time and
 build
 it instead when it becomes available.  It's good to debug the build
 process though because it can be painful building from source.

Re: IMPORTANT: Commit rules for next week's rampdown to M5

[Kevin Rushforth]

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 up Monday evening if all goes well.


-- Kevin


Kevin Rushforth wrote:

TO: ALL JAVAFX DEVELOPERS

Next week is our ramp-down week for M5, which is the last milestone 
before we fork the 8u20 stabilization repo. As a reminder, the 
Milestone Week stabilization rules [1] are in effect for any 
changesets pushed after 1am on Monday, June 16. This means no 
post-commit reviews, and you need an extra "+1" from one of the leads 
listed on the Wiki (the usual exception applies for javadoc changes 
and changes that don't touch the shipping bits).


Given that this is the last milestone before 8u20 goes into its 
end-of-the-release stabilization we are likely to be a bit more strict 
than previous milestones about giving approval. Pretty much if it 
isn't a regression or a serious bug, it will likely need to wait for 
8u40.


-- Steve & Kevin

[1] https://wiki.openjdk.java.net/display/OpenJFX/8u20

Re: Testing accessibility / sample apps

[Jann Schneider]

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
NativeCompileTask.compile() on task ':fxpackager:buildJavaPackager'
...
Caused by: java.util.concurrent.ExecutionException:
org.gradle.process.internal.ExecException: A problem occurred starting
process 'command 'C:/Program Files (x86)/Microsoft Visual Studio
10.0/VC/BIN/amd64/cl.exe''
...
Caused by: java.io.IOException: Cannot run program "C:/Program Files
(x86)/Microsoft Visual Studio 10.0/VC/BIN/amd64/cl.exe" (in directory
"D:\jann\sandbox\java\openjfx\modules\fxpackager"): CreateProcess
error=2, Das System kann die angegebene Datei nicht finden
...
Caused by: java.io.IOException: CreateProcess error=2, Das System kann
die angegebene Datei nicht finden (file not found)

Actually cl.exe is located at: C:\Program Files (x86)\Microsoft Visual
Studio 10.0\VC\bin - but it looks for ...bin/amd64/cl.exe

I've also tried to run the build from the cygwin terminal and as well
from the visual studio command prompt where i could call cl.exe
directly .. Always the same result.

Is there a parameter to specify where theVS compiler and stuff is
located? btw. i checked that the %VS100COMNTools% variable is set
properly.

What else could i check? Thanks in advance :)

Jann




2014-06-20 23:30 GMT+02:00, Kevin Rushforth :
>
>> * What went wrong:
>> Execution failed for task ':fxpackager:buildJavaPackager'.
>>
>> Could not call NativeCompileTask.compile() on task
>> ':fxpackager:buildJavaPackager'
>
> When I've seen this in the past it's been related to the compiler
> install. Do you have VS 2010 SP1 or something else?
>
> -- Kevin
>
>
>
> 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
>> This works as expected! When running
>> $ gradle sdk
>> or just gradle without any target i get the following error:
>>
>> FAILURE: Build failed with an exception.
>>
>> * What went wrong:
>> Execution failed for task ':fxpackager:buildJavaPackager'.
>>
>>> Could not call NativeCompileTask.compile() on task
>>> ':fxpackager:buildJavaPackager'
>>>
>>
>> Is this a "known issue" and do you know what's going wrong here?
>> Should i post more "info" or "debug" output, too?
>>
>> Thanks
>> Jann
>>
>>
>>
>> 2014-06-20 21:58 GMT+02:00, Stephen F Northover
>> :
>>
>>> 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 problems.
>
> Regards Jann
>
> 2014-06-20 19:27 GMT+02:00, Kevin Rushforth
> :
>
>> 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 you don't need to build WebKit. We would be
>> interested in hearing whether the instructions on the Wiki are
>> sufficient for you to get the build working.
>>
>> -- Kevin
>>
>>
>> Stephen F Northover wrote:
>>
>>> 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 release at that time and build
>>> it instead when it becomes available.  It's good to debug the build
>>> process though because it can be painful building from source.
>>>
>>> Steve
>>>
>>> On 2014-06-20, 12:43 PM, Jann Schneider wrote:
>>>
 Hi all,

 @Steven: thx for the links. I'll try to build the openjfx project
 on
 the windows 7 notebook and test the sample apps with NVDA then.
 Today i tried the latest ea of jdk1.8.0_20 and sample apps with
 nvda
 14.2. Unfortunately i was not able to read anything except the
 window
 title.
 I've just installed the jdk, changed my JAVA_HOME and tried to run
 e.g. the ensemble.jar
 $ java -jar ensemble.jar -Djavafx.accessible.force=true

 Well i'll try it again by means of building javafx from source and
 post my results back to the list.
>>>

Re: Testing accessibility / sample apps

[Kevin Rushforth]

* What went wrong:
Execution failed for task ':fxpackager:buildJavaPackager'.

Could not call NativeCompileTask.compile() on task 
':fxpackager:buildJavaPackager'


When I've seen this in the past it's been related to the compiler 
install. Do you have VS 2010 SP1 or something else?


-- Kevin



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
This works as expected! When running
$ gradle sdk
or just gradle without any target i get the following error:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':fxpackager:buildJavaPackager'.
  

Could not call NativeCompileTask.compile() on task 
':fxpackager:buildJavaPackager'



Is this a "known issue" and do you know what's going wrong here?
Should i post more "info" or "debug" output, too?

Thanks
Jann



2014-06-20 21:58 GMT+02:00, Stephen F Northover :
  

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 problems.

Regards Jann

2014-06-20 19:27 GMT+02:00, Kevin Rushforth
:


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 you don't need to build WebKit. We would be
interested in hearing whether the instructions on the Wiki are
sufficient for you to get the build working.

-- Kevin


Stephen F Northover wrote:
  

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 release at that time and build
it instead when it becomes available.  It's good to debug the build
process though because it can be painful building from source.

Steve

On 2014-06-20, 12:43 PM, Jann Schneider wrote:


Hi all,

@Steven: thx for the links. I'll try to build the openjfx project on
the windows 7 notebook and test the sample apps with NVDA then.
Today i tried the latest ea of jdk1.8.0_20 and sample apps with nvda
14.2. Unfortunately i was not able to read anything except the window
title.
I've just installed the jdk, changed my JAVA_HOME and tried to run
e.g. the ensemble.jar
$ java -jar ensemble.jar -Djavafx.accessible.force=true

Well i'll try it again by means of building javafx from source and
post my results back to the list.

Regards Jann!


2014-06-20 14:46 GMT+02:00, Stephen F Northover
:
  

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 the
best way to work with the team anyway because you can get fixes
as they
are made.  EA builds take a while to come out and there is no
substitute
for running on the latest code base.

Unfortunately due to Microsoft, building OpenJFX is a bit harder on
Windows.  However, it is doable and the build instructions should be
complete.  If they are not (and if you hit any problems), please
post
back to this list.

Here are the build instructions:

https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX

Many committers use an IDE (you don't have to) and OpenJFX is
supports
the three major IDE vendors:

https://wiki.openjdk.java.net/display/OpenJFX/Using+an+IDE

Looking forward to working with you,
Steve

On 2014-06-19, 7:10 PM, Felipe Heidrich wrote:


Hi Jann,

Unfortunately Linux support is not in the plan for 8u40.

Windows 7 is supported and we have recently fixed JAWS support (see
https://javafx-jira.kenai.com/browse/RT-37530 and
https://javafx-jira.kenai.com/browse/RT-37609).
Unfortunately due to the 8u20 to 8u40 transition the code has not
being
released yet, but soon.

The majority of our testing was done using Narrator. That said,
I also
tested NVDA lastest version on Windows 8 and I didn’t see any major
problems.
On the Mac we tested with VoiceOver.

Regards,
Felipe


On Jun 19, 2014, at 2:24 PM, Jann Schneider
 wrote:

  

Hello all,

As a blind java developer i'm interessted in testing the
accessibility of
JavaFX and maybe help to find some issues.

I've just set up my build environment on my ubuntu 14.04 laptop
and
checked out the project files as described in the wiki. I could
also set
it up on a windows 7 wi

Re: Testing accessibility / sample apps

[Stephen F Northover]

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
This works as expected! When running
$ gradle sdk
or just gradle without any target i get the following error:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':fxpackager:buildJavaPackager'.

Could not call NativeCompileTask.compile() on task 
':fxpackager:buildJavaPackager'

Is this a "known issue" and do you know what's going wrong here?
Should i post more "info" or "debug" output, too?

Thanks
Jann



2014-06-20 21:58 GMT+02:00, Stephen F Northover :

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 problems.

Regards Jann

2014-06-20 19:27 GMT+02:00, Kevin Rushforth
:

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 you don't need to build WebKit. We would be
interested in hearing whether the instructions on the Wiki are
sufficient for you to get the build working.

-- Kevin


Stephen F Northover wrote:

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 release at that time and build
it instead when it becomes available.  It's good to debug the build
process though because it can be painful building from source.

Steve

On 2014-06-20, 12:43 PM, Jann Schneider wrote:

Hi all,

@Steven: thx for the links. I'll try to build the openjfx project on
the windows 7 notebook and test the sample apps with NVDA then.
Today i tried the latest ea of jdk1.8.0_20 and sample apps with nvda
14.2. Unfortunately i was not able to read anything except the window
title.
I've just installed the jdk, changed my JAVA_HOME and tried to run
e.g. the ensemble.jar
$ java -jar ensemble.jar -Djavafx.accessible.force=true

Well i'll try it again by means of building javafx from source and
post my results back to the list.

Regards Jann!


2014-06-20 14:46 GMT+02:00, Stephen F Northover
:

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 the
best way to work with the team anyway because you can get fixes
as they
are made.  EA builds take a while to come out and there is no
substitute
for running on the latest code base.

Unfortunately due to Microsoft, building OpenJFX is a bit harder on
Windows.  However, it is doable and the build instructions should be
complete.  If they are not (and if you hit any problems), please
post
back to this list.

Here are the build instructions:

https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX

Many committers use an IDE (you don't have to) and OpenJFX is
supports
the three major IDE vendors:

https://wiki.openjdk.java.net/display/OpenJFX/Using+an+IDE

Looking forward to working with you,
Steve

On 2014-06-19, 7:10 PM, Felipe Heidrich wrote:

Hi Jann,

Unfortunately Linux support is not in the plan for 8u40.

Windows 7 is supported and we have recently fixed JAWS support (see
https://javafx-jira.kenai.com/browse/RT-37530 and
https://javafx-jira.kenai.com/browse/RT-37609).
Unfortunately due to the 8u20 to 8u40 transition the code has not
being
released yet, but soon.

The majority of our testing was done using Narrator. That said,
I also
tested NVDA lastest version on Windows 8 and I didn’t see any major
problems.
On the Mac we tested with VoiceOver.

Regards,
Felipe


On Jun 19, 2014, at 2:24 PM, Jann Schneider
 wrote:


Hello all,

As a blind java developer i'm interessted in testing the
accessibility of
JavaFX and maybe help to find some issues.

I've just set up my build environment on my ubuntu 14.04 laptop
and
checked out the project files as described in the wiki. I could
also set
it up on a windows 7 with Jaws 15 and NVDa (don't know what the
current
version is) for comparison..

No i am wondering if there are some examples i could try?

Regards Jann

Re: Testing accessibility / sample apps

[Jann Schneider]

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 an exception.

* What went wrong:
Execution failed for task ':fxpackager:buildJavaPackager'.
> Could not call NativeCompileTask.compile() on task 
> ':fxpackager:buildJavaPackager'

Is this a "known issue" and do you know what's going wrong here?
Should i post more "info" or "debug" output, too?

Thanks
Jann



2014-06-20 21:58 GMT+02:00, Stephen F Northover :
> 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 problems.
>>>
>>> Regards Jann
>>>
>>> 2014-06-20 19:27 GMT+02:00, Kevin Rushforth
>>> :
 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 you don't need to build WebKit. We would be
 interested in hearing whether the instructions on the Wiki are
 sufficient for you to get the build working.

 -- Kevin


 Stephen F Northover wrote:
> 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 release at that time and build
> it instead when it becomes available.  It's good to debug the build
> process though because it can be painful building from source.
>
> Steve
>
> On 2014-06-20, 12:43 PM, Jann Schneider wrote:
>> Hi all,
>>
>> @Steven: thx for the links. I'll try to build the openjfx project on
>> the windows 7 notebook and test the sample apps with NVDA then.
>> Today i tried the latest ea of jdk1.8.0_20 and sample apps with nvda
>> 14.2. Unfortunately i was not able to read anything except the window
>> title.
>> I've just installed the jdk, changed my JAVA_HOME and tried to run
>> e.g. the ensemble.jar
>> $ java -jar ensemble.jar -Djavafx.accessible.force=true
>>
>> Well i'll try it again by means of building javafx from source and
>> post my results back to the list.
>>
>> Regards Jann!
>>
>>
>> 2014-06-20 14:46 GMT+02:00, Stephen F Northover
>> :
>>> 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 the
>>> best way to work with the team anyway because you can get fixes
>>> as they
>>> are made.  EA builds take a while to come out and there is no
>>> substitute
>>> for running on the latest code base.
>>>
>>> Unfortunately due to Microsoft, building OpenJFX is a bit harder on
>>> Windows.  However, it is doable and the build instructions should be
>>> complete.  If they are not (and if you hit any problems), please
>>> post
>>> back to this list.
>>>
>>> Here are the build instructions:
>>>
>>> https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX
>>>
>>> Many committers use an IDE (you don't have to) and OpenJFX is
>>> supports
>>> the three major IDE vendors:
>>>
>>> https://wiki.openjdk.java.net/display/OpenJFX/Using+an+IDE
>>>
>>> Looking forward to working with you,
>>> Steve
>>>
>>> On 2014-06-19, 7:10 PM, Felipe Heidrich wrote:
 Hi Jann,

 Unfortunately Linux support is not in the plan for 8u40.

 Windows 7 is supported and we have recently fixed JAWS support (see
 https://javafx-jira.kenai.com/browse/RT-37530 and
 https://javafx-jira.kenai.com/browse/RT-37609).
 Unfortunately due to the 8u20 to 8u40 transition the code has not
 being
 released yet, but soon.

 The majority of our testing was done using Narrator. That said,
 I also
 tested NVDA lastest version on Windows 8 and I didn’t see any major
 problems.
 On the Mac we tested with VoiceOver.

 Regards,
 Felipe


>>>

Re: Dialogs in JavaFX

[Jonathan Giles]

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 implied "Type" of 
the DialogBox and response:

// Type Message: No response
DialogBox dbox = new DialogBox("FYI"); dbox.setMessage("Just 
saying...");
dbox.showMessageDialog(focusedNode);

// Type Confirm: Boolean response
DialogBox dbox = new DialogBox("Sanity Check"); 
dbox.setMessage("Really???");
boolean response = dbox.showConfirmDialog(focusedNode);

// Type Option: Integer response
DialogBox dbox = new DialogBox("Which One"); dbox.setMessage("Select 
One"); dbox.setOptions(myOptions);
int response = dbox.showOptionDialog(focusedNode, defaultOption);

// Type Input: String response
DialogBox dbox = new DialogBox("Tell Me"); dbox.setMessage("Tell me what you 
want:");
String response = xbox.showOptionDialog(focusedNode, default);

The only alternative I see would be to explicitly set a DialogBox type and 
return a DialogBoxResponse, which could embody any of the above. That seems 
cumbersome to me. I also think it would be over-engineering to try to support 
any kind of response (say like a Color or a Font). In these cases, I think it's 
better to have your ColorChooserPane or FontChooserPane act as content:

// Type ColorChooser: Boolean response plus Color
DialogBox dbox = new DialogBox("Please Pick a Color"); 
dbox.setContent(myColorChooserPane);
if(dbox.showConfirmPanel(focusedNode))
setColor(myColorChooserPane.getSelectedColor());

In fact, your ColorChooserPane could have a showColorDialog() method that would 
just be the above code.

Jeff Martin

On Jun 20, 2014, at 10:15 AM, Stephen F Northover 
 wrote:


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 issues.  The downside is that JIRA does not 
provide threaded conversations and it can be hard to follow.

Steve

On 2014-06-20, 9:41 AM, Jeff Martin wrote:

That is a great post. I think the big problem with dialogs in Swing was the 
permutations problem. There were four basic types of dialogs (Message, Confirm, 
Option, Input) with six different parameters (Title, Message, Icon, Content, 
MessageType, Options) - so JOptionPane ended up with a sea of static methods 
that were confusing to navigate.

I don't think you could go wrong with a simple DialogBox class like this (I 
love simple):

// Constructor
public DialogBox(String aTitle);

// Options
public String getTitle();
public void setTitle(String aTitle);
public String getMessage();
public void setMessage(String aMessage);
public MessageType getMessageType();
public void setMessageType(MessageType aMessageType);
public Node getContent();
public void setContent(Node aNode);
public Node getGraphic();
public void setGraphic(Node aNode);
public String[] getOptions();
public void setOptions(String ... theOptions);

// Convenience methods to set Message + MessageType
public void setErrorMessage(String aMessage);
public void setWarningMessage(String aMessage);
public void setQuestionMessage(String aMessage);

// Show methods
public void showMessageDialog(T aComp);
public boolean showConfirmDialog(T aComp);
public int showOptionDialog(T aComp, String aDefault);
public String showInputDialog(T aComp, String aDefault);

// Programatic dismissal
public void confirm();
public void cancel();

Then most common invocations would look something like this:

// Get user confirmation
DialogBox dbox = new DialogBox("Sanity Check");
dbox.setWarningMessage("Are you sure you want to do this? It could kill 
you.");
if(!dbox.showConfirmationDialog(focusedNode)) return;

Using instance methods instead of static methods gives opportunity to subclass 
and override various methods. And notice the Content attribute - for the 
standard case when no Content is provided, it is built programmatically based 
on the parameters (essentially just the message and either an Option combo, an 
input textfield or nothing).

I've been using this in my JavaFX app for a while and it is working great and 
makes porting from Swing easy. I even built it on a convenient FormBuilder 
class that makes building a simple stack of form controls easy, and can also be 
used for advanced DialogBoxes.

Jeff Martin
214.513.1636


On Jun 20, 

Re: Testing accessibility / sample apps

[Stephen F Northover]

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 problems.

Regards Jann

2014-06-20 19:27 GMT+02:00, Kevin Rushforth 
:

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 you don't need to build WebKit. We would be
interested in hearing whether the instructions on the Wiki are
sufficient for you to get the build working.

-- Kevin


Stephen F Northover wrote:

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 release at that time and build
it instead when it becomes available.  It's good to debug the build
process though because it can be painful building from source.

Steve

On 2014-06-20, 12:43 PM, Jann Schneider wrote:

Hi all,

@Steven: thx for the links. I'll try to build the openjfx project on
the windows 7 notebook and test the sample apps with NVDA then.
Today i tried the latest ea of jdk1.8.0_20 and sample apps with nvda
14.2. Unfortunately i was not able to read anything except the window
title.
I've just installed the jdk, changed my JAVA_HOME and tried to run
e.g. the ensemble.jar
$ java -jar ensemble.jar -Djavafx.accessible.force=true

Well i'll try it again by means of building javafx from source and
post my results back to the list.

Regards Jann!


2014-06-20 14:46 GMT+02:00, Stephen F Northover
:

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 the
best way to work with the team anyway because you can get fixes 
as they

are made.  EA builds take a while to come out and there is no
substitute
for running on the latest code base.

Unfortunately due to Microsoft, building OpenJFX is a bit harder on
Windows.  However, it is doable and the build instructions should be
complete.  If they are not (and if you hit any problems), please 
post

back to this list.

Here are the build instructions:

https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX

Many committers use an IDE (you don't have to) and OpenJFX is 
supports

the three major IDE vendors:

https://wiki.openjdk.java.net/display/OpenJFX/Using+an+IDE

Looking forward to working with you,
Steve

On 2014-06-19, 7:10 PM, Felipe Heidrich wrote:

Hi Jann,

Unfortunately Linux support is not in the plan for 8u40.

Windows 7 is supported and we have recently fixed JAWS support (see
https://javafx-jira.kenai.com/browse/RT-37530 and
https://javafx-jira.kenai.com/browse/RT-37609).
Unfortunately due to the 8u20 to 8u40 transition the code has not
being
released yet, but soon.

The majority of our testing was done using Narrator. That said, 
I also

tested NVDA lastest version on Windows 8 and I didn’t see any major
problems.
On the Mac we tested with VoiceOver.

Regards,
Felipe


On Jun 19, 2014, at 2:24 PM, Jann Schneider
 wrote:


Hello all,

As a blind java developer i'm interessted in testing the
accessibility of
JavaFX and maybe help to find some issues.

I've just set up my build environment on my ubuntu 14.04 laptop 
and

checked out the project files as described in the wiki. I could
also set
it up on a windows 7 with Jaws 15 and NVDa (don't know what the
current
version is) for comparison..

No i am wondering if there are some examples i could try?

Regards Jann

Re: Testing accessibility / sample apps

[Kevin Rushforth]

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 :
  

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 you don't need to build WebKit. We would be
interested in hearing whether the instructions on the Wiki are
sufficient for you to get the build working.

-- Kevin


Stephen F Northover wrote:


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 release at that time and build
it instead when it becomes available.  It's good to debug the build
process though because it can be painful building from source.

Steve

On 2014-06-20, 12:43 PM, Jann Schneider wrote:
  

Hi all,

@Steven: thx for the links. I'll try to build the openjfx project on
the windows 7 notebook and test the sample apps with NVDA then.
Today i tried the latest ea of jdk1.8.0_20 and sample apps with nvda
14.2. Unfortunately i was not able to read anything except the window
title.
I've just installed the jdk, changed my JAVA_HOME and tried to run
e.g. the ensemble.jar
$ java -jar ensemble.jar -Djavafx.accessible.force=true

Well i'll try it again by means of building javafx from source and
post my results back to the list.

Regards Jann!


2014-06-20 14:46 GMT+02:00, Stephen F Northover
:


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 the
best way to work with the team anyway because you can get fixes as they
are made.  EA builds take a while to come out and there is no
substitute
for running on the latest code base.

Unfortunately due to Microsoft, building OpenJFX is a bit harder on
Windows.  However, it is doable and the build instructions should be
complete.  If they are not (and if you hit any problems), please post
back to this list.

Here are the build instructions:

  https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX

Many committers use an IDE (you don't have to) and OpenJFX is supports
the three major IDE vendors:

  https://wiki.openjdk.java.net/display/OpenJFX/Using+an+IDE

Looking forward to working with you,
Steve

On 2014-06-19, 7:10 PM, Felipe Heidrich wrote:
  

Hi Jann,

Unfortunately Linux support is not in the plan for 8u40.

Windows 7 is supported and we have recently fixed JAWS support (see
https://javafx-jira.kenai.com/browse/RT-37530 and
https://javafx-jira.kenai.com/browse/RT-37609).
Unfortunately due to the 8u20 to 8u40 transition the code has not
being
released yet, but soon.

The majority of our testing was done using Narrator. That said, I also
tested NVDA lastest version on Windows 8 and I didn’t see any major
problems.
On the Mac we tested with VoiceOver.

Regards,
Felipe


On Jun 19, 2014, at 2:24 PM, Jann Schneider
 wrote:



Hello all,

As a blind java developer i'm interessted in testing the
accessibility of
JavaFX and maybe help to find some issues.

I've just set up my build environment on my ubuntu 14.04 laptop and
checked out the project files as described in the wiki. I could
also set
it up on a windows 7 with Jaws 15 and NVDa (don't know what the
current
version is) for comparison..

No i am wondering if there are some examples i could try?

Regards Jann


  

Re: Testing accessibility / sample apps

[Jann Schneider]

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 :
> 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 you don't need to build WebKit. We would be
> interested in hearing whether the instructions on the Wiki are
> sufficient for you to get the build working.
>
> -- Kevin
>
>
> Stephen F Northover wrote:
>> 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 release at that time and build
>> it instead when it becomes available.  It's good to debug the build
>> process though because it can be painful building from source.
>>
>> Steve
>>
>> On 2014-06-20, 12:43 PM, Jann Schneider wrote:
>>> Hi all,
>>>
>>> @Steven: thx for the links. I'll try to build the openjfx project on
>>> the windows 7 notebook and test the sample apps with NVDA then.
>>> Today i tried the latest ea of jdk1.8.0_20 and sample apps with nvda
>>> 14.2. Unfortunately i was not able to read anything except the window
>>> title.
>>> I've just installed the jdk, changed my JAVA_HOME and tried to run
>>> e.g. the ensemble.jar
>>> $ java -jar ensemble.jar -Djavafx.accessible.force=true
>>>
>>> Well i'll try it again by means of building javafx from source and
>>> post my results back to the list.
>>>
>>> Regards Jann!
>>>
>>>
>>> 2014-06-20 14:46 GMT+02:00, Stephen F Northover
>>> :
 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 the
 best way to work with the team anyway because you can get fixes as they
 are made.  EA builds take a while to come out and there is no
 substitute
 for running on the latest code base.

 Unfortunately due to Microsoft, building OpenJFX is a bit harder on
 Windows.  However, it is doable and the build instructions should be
 complete.  If they are not (and if you hit any problems), please post
 back to this list.

 Here are the build instructions:

   https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX

 Many committers use an IDE (you don't have to) and OpenJFX is supports
 the three major IDE vendors:

   https://wiki.openjdk.java.net/display/OpenJFX/Using+an+IDE

 Looking forward to working with you,
 Steve

 On 2014-06-19, 7:10 PM, Felipe Heidrich wrote:
> Hi Jann,
>
> Unfortunately Linux support is not in the plan for 8u40.
>
> Windows 7 is supported and we have recently fixed JAWS support (see
> https://javafx-jira.kenai.com/browse/RT-37530 and
> https://javafx-jira.kenai.com/browse/RT-37609).
> Unfortunately due to the 8u20 to 8u40 transition the code has not
> being
> released yet, but soon.
>
> The majority of our testing was done using Narrator. That said, I also
> tested NVDA lastest version on Windows 8 and I didn’t see any major
> problems.
> On the Mac we tested with VoiceOver.
>
> Regards,
> Felipe
>
>
> On Jun 19, 2014, at 2:24 PM, Jann Schneider
>  wrote:
>
>> Hello all,
>>
>> As a blind java developer i'm interessted in testing the
>> accessibility of
>> JavaFX and maybe help to find some issues.
>>
>> I've just set up my build environment on my ubuntu 14.04 laptop and
>> checked out the project files as described in the wiki. I could
>> also set
>> it up on a windows 7 with Jaws 15 and NVDa (don't know what the
>> current
>> version is) for comparison..
>>
>> No i am wondering if there are some examples i could try?
>>
>> Regards Jann
>>
>>

>>
>

Re: JavaFX at JavaOne 2014

[Mike]

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> wrote:

> Unfortunately there's nothing new and no Oracle sessions on that subject -
> javafx on ios and/or android...
>
> :(
>
> --
> Pedro Duque Vieira
>

Re: Testing accessibility / sample apps

[Kevin Rushforth]

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 you don't need to build WebKit. We would be 
interested in hearing whether the instructions on the Wiki are 
sufficient for you to get the build working.


-- Kevin


Stephen F Northover wrote:

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 release at that time and build 
it instead when it becomes available.  It's good to debug the build 
process though because it can be painful building from source.


Steve

On 2014-06-20, 12:43 PM, Jann Schneider wrote:

Hi all,

@Steven: thx for the links. I'll try to build the openjfx project on
the windows 7 notebook and test the sample apps with NVDA then.
Today i tried the latest ea of jdk1.8.0_20 and sample apps with nvda
14.2. Unfortunately i was not able to read anything except the window
title.
I've just installed the jdk, changed my JAVA_HOME and tried to run
e.g. the ensemble.jar
$ java -jar ensemble.jar -Djavafx.accessible.force=true

Well i'll try it again by means of building javafx from source and
post my results back to the list.

Regards Jann!


2014-06-20 14:46 GMT+02:00, Stephen F Northover 
:

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 the
best way to work with the team anyway because you can get fixes as they
are made.  EA builds take a while to come out and there is no 
substitute

for running on the latest code base.

Unfortunately due to Microsoft, building OpenJFX is a bit harder on
Windows.  However, it is doable and the build instructions should be
complete.  If they are not (and if you hit any problems), please post
back to this list.

Here are the build instructions:

  https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX

Many committers use an IDE (you don't have to) and OpenJFX is supports
the three major IDE vendors:

  https://wiki.openjdk.java.net/display/OpenJFX/Using+an+IDE

Looking forward to working with you,
Steve

On 2014-06-19, 7:10 PM, Felipe Heidrich wrote:

Hi Jann,

Unfortunately Linux support is not in the plan for 8u40.

Windows 7 is supported and we have recently fixed JAWS support (see
https://javafx-jira.kenai.com/browse/RT-37530 and
https://javafx-jira.kenai.com/browse/RT-37609).
Unfortunately due to the 8u20 to 8u40 transition the code has not 
being

released yet, but soon.

The majority of our testing was done using Narrator. That said, I also
tested NVDA lastest version on Windows 8 and I didn’t see any major
problems.
On the Mac we tested with VoiceOver.

Regards,
Felipe


On Jun 19, 2014, at 2:24 PM, Jann Schneider
 wrote:


Hello all,

As a blind java developer i'm interessted in testing the 
accessibility of

JavaFX and maybe help to find some issues.

I've just set up my build environment on my ubuntu 14.04 laptop and
checked out the project files as described in the wiki. I could 
also set
it up on a windows 7 with Jaws 15 and NVDa (don't know what the 
current

version is) for comparison..

No i am wondering if there are some examples i could try?

Regards Jann

Review request for adding capability to disable Lens builds

[David Hill]

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/ 


As part of this change we have:
  * added an includeMonocle toggle (with a default of false)
  * when includeMonocle is false, will exclude java Glass classes from 
jfxrt.jar.
* javafx.platform.properties and javafx.properties should have a ending 
newline
  * for (armv*, x86egl)
  * includeLens, includeMonocle, includeGTK will toggle native building and 
inclusion of Java Glass classes
  * javafx.platform.properties will only include the groups that were built
  * definitions of compiler/linker had migrated down in the buildSrc files, 
so were moved back up for clarity.

Tested by clean building with includeLens, includeMonocle, includeGTK turned 
off in test builds.
This submit should have no current build result changes except for the extra 
newline on javafx.*.properties and a small amount of reordering of 
javafx.platform.properties

--
David Hill 
Java Embedded Development

"This email was created using 100% recycled electrons."

Re: Testing accessibility / sample apps

[Stephen F Northover]

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 release at that time and build it 
instead when it becomes available.  It's good to debug the build process 
though because it can be painful building from source.


Steve

On 2014-06-20, 12:43 PM, Jann Schneider wrote:

Hi all,

@Steven: thx for the links. I'll try to build the openjfx project on
the windows 7 notebook and test the sample apps with NVDA then.
Today i tried the latest ea of jdk1.8.0_20 and sample apps with nvda
14.2. Unfortunately i was not able to read anything except the window
title.
I've just installed the jdk, changed my JAVA_HOME and tried to run
e.g. the ensemble.jar
$ java -jar ensemble.jar -Djavafx.accessible.force=true

Well i'll try it again by means of building javafx from source and
post my results back to the list.

Regards Jann!


2014-06-20 14:46 GMT+02:00, Stephen F Northover :

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 the
best way to work with the team anyway because you can get fixes as they
are made.  EA builds take a while to come out and there is no substitute
for running on the latest code base.

Unfortunately due to Microsoft, building OpenJFX is a bit harder on
Windows.  However, it is doable and the build instructions should be
complete.  If they are not (and if you hit any problems), please post
back to this list.

Here are the build instructions:

  https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX

Many committers use an IDE (you don't have to) and OpenJFX is supports
the three major IDE vendors:

  https://wiki.openjdk.java.net/display/OpenJFX/Using+an+IDE

Looking forward to working with you,
Steve

On 2014-06-19, 7:10 PM, Felipe Heidrich wrote:

Hi Jann,

Unfortunately Linux support is not in the plan for 8u40.

Windows 7 is supported and we have recently fixed JAWS support (see
https://javafx-jira.kenai.com/browse/RT-37530 and
https://javafx-jira.kenai.com/browse/RT-37609).
Unfortunately due to the 8u20 to 8u40 transition the code has not being
released yet, but soon.

The majority of our testing was done using Narrator. That said, I also
tested NVDA lastest version on Windows 8 and I didn’t see any major
problems.
On the Mac we tested with VoiceOver.

Regards,
Felipe


On Jun 19, 2014, at 2:24 PM, Jann Schneider
 wrote:


Hello all,

As a blind java developer i'm interessted in testing the accessibility of
JavaFX and maybe help to find some issues.

I've just set up my build environment on my ubuntu 14.04 laptop and
checked out the project files as described in the wiki. I could also set
it up on a windows 7 with Jaws 15 and NVDa (don't know what the current
version is) for comparison..

No i am wondering if there are some examples i could try?

Regards Jann

Re: Testing accessibility / sample apps

[Jann Schneider]

Hi all,

@Steven: thx for the links. I'll try to build the openjfx project on
the windows 7 notebook and test the sample apps with NVDA then.
Today i tried the latest ea of jdk1.8.0_20 and sample apps with nvda
14.2. Unfortunately i was not able to read anything except the window
title.
I've just installed the jdk, changed my JAVA_HOME and tried to run
e.g. the ensemble.jar
$ java -jar ensemble.jar -Djavafx.accessible.force=true

Well i'll try it again by means of building javafx from source and
post my results back to the list.

Regards Jann!


2014-06-20 14:46 GMT+02:00, Stephen F Northover :
> 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 the
> best way to work with the team anyway because you can get fixes as they
> are made.  EA builds take a while to come out and there is no substitute
> for running on the latest code base.
>
> Unfortunately due to Microsoft, building OpenJFX is a bit harder on
> Windows.  However, it is doable and the build instructions should be
> complete.  If they are not (and if you hit any problems), please post
> back to this list.
>
> Here are the build instructions:
>
>  https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX
>
> Many committers use an IDE (you don't have to) and OpenJFX is supports
> the three major IDE vendors:
>
>  https://wiki.openjdk.java.net/display/OpenJFX/Using+an+IDE
>
> Looking forward to working with you,
> Steve
>
> On 2014-06-19, 7:10 PM, Felipe Heidrich wrote:
>> Hi Jann,
>>
>> Unfortunately Linux support is not in the plan for 8u40.
>>
>> Windows 7 is supported and we have recently fixed JAWS support (see
>> https://javafx-jira.kenai.com/browse/RT-37530 and
>> https://javafx-jira.kenai.com/browse/RT-37609).
>> Unfortunately due to the 8u20 to 8u40 transition the code has not being
>> released yet, but soon.
>>
>> The majority of our testing was done using Narrator. That said, I also
>> tested NVDA lastest version on Windows 8 and I didn’t see any major
>> problems.
>> On the Mac we tested with VoiceOver.
>>
>> Regards,
>> Felipe
>>
>>
>> On Jun 19, 2014, at 2:24 PM, Jann Schneider
>>  wrote:
>>
>>> Hello all,
>>>
>>> As a blind java developer i'm interessted in testing the accessibility of
>>> JavaFX and maybe help to find some issues.
>>>
>>> I've just set up my build environment on my ubuntu 14.04 laptop and
>>> checked out the project files as described in the wiki. I could also set
>>> it up on a windows 7 with Jaws 15 and NVDa (don't know what the current
>>> version is) for comparison..
>>>
>>> No i am wondering if there are some examples i could try?
>>>
>>> Regards Jann
>>>
>>>
>
>

Re: JavaFX at JavaOne 2014

[Pedro Duque Vieira]

Unfortunately there's nothing new and no Oracle sessions on that subject -
javafx on ios and/or android...

:(

-- 
Pedro Duque Vieira

Re: Dialogs in JavaFX

[Jeff Martin]

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 
saying...");
dbox.showMessageDialog(focusedNode);

// Type Confirm: Boolean response
DialogBox dbox = new DialogBox("Sanity Check"); 
dbox.setMessage("Really???");
boolean response = dbox.showConfirmDialog(focusedNode);

// Type Option: Integer response
DialogBox dbox = new DialogBox("Which One"); dbox.setMessage("Select 
One"); dbox.setOptions(myOptions);
int response = dbox.showOptionDialog(focusedNode, defaultOption);

// Type Input: String response
DialogBox dbox = new DialogBox("Tell Me"); dbox.setMessage("Tell me 
what you want:");
String response = xbox.showOptionDialog(focusedNode, default);

The only alternative I see would be to explicitly set a DialogBox type and 
return a DialogBoxResponse, which could embody any of the above. That seems 
cumbersome to me. I also think it would be over-engineering to try to support 
any kind of response (say like a Color or a Font). In these cases, I think it's 
better to have your ColorChooserPane or FontChooserPane act as content:

// Type ColorChooser: Boolean response plus Color
DialogBox dbox = new DialogBox("Please Pick a Color"); 
dbox.setContent(myColorChooserPane);
if(dbox.showConfirmPanel(focusedNode))
setColor(myColorChooserPane.getSelectedColor());

In fact, your ColorChooserPane could have a showColorDialog() method that would 
just be the above code.

Jeff Martin

On Jun 20, 2014, at 10:15 AM, Stephen F Northover 
 wrote:

> 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 issues.  The downside is that JIRA does 
> not provide threaded conversations and it can be hard to follow.
> 
> Steve
> 
> On 2014-06-20, 9:41 AM, Jeff Martin wrote:
>> That is a great post. I think the big problem with dialogs in Swing was the 
>> permutations problem. There were four basic types of dialogs (Message, 
>> Confirm, Option, Input) with six different parameters (Title, Message, Icon, 
>> Content, MessageType, Options) - so JOptionPane ended up with a sea of 
>> static methods that were confusing to navigate.
>> 
>> I don't think you could go wrong with a simple DialogBox class like this (I 
>> love simple):
>> 
>>  // Constructor
>>  public DialogBox(String aTitle);
>> 
>>  // Options
>>  public String getTitle();
>>  public void setTitle(String aTitle);
>>  public String getMessage();
>>  public void setMessage(String aMessage);
>>  public MessageType getMessageType();
>>  public void setMessageType(MessageType aMessageType);
>>  public Node getContent();
>>  public void setContent(Node aNode);
>>  public Node getGraphic();
>>  public void setGraphic(Node aNode);
>>  public String[] getOptions();
>>  public void setOptions(String ... theOptions);
>> 
>>  // Convenience methods to set Message + MessageType
>>  public void setErrorMessage(String aMessage);
>>  public void setWarningMessage(String aMessage);
>>  public void setQuestionMessage(String aMessage);
>> 
>>  // Show methods
>>  public void showMessageDialog(T aComp);
>>  public boolean showConfirmDialog(T aComp);
>>  public int showOptionDialog(T aComp, String aDefault);
>>  public String showInputDialog(T aComp, String aDefault);
>> 
>>  // Programatic dismissal
>>  public void confirm();
>>  public void cancel();
>> 
>> Then most common invocations would look something like this:
>> 
>>  // Get user confirmation
>>  DialogBox dbox = new DialogBox("Sanity Check");
>>  dbox.setWarningMessage("Are you sure you want to do this? It could kill 
>> you.");
>>  if(!dbox.showConfirmationDialog(focusedNode)) return;
>> 
>> Using instance methods instead of static methods gives opportunity to 
>> subclass and override various methods. And notice the Content attribute - 
>> for the standard case when no Content is provided, it is built 
>> programmatically based on the parameters (essentially just the message and 
>> either an Option combo, an input textfield or nothing).
>> 
>> I've been using this in my JavaFX app for a while and it is working great 
>> and makes porting from Swing easy. I even built it on a convenient 
>> FormBuilder class that makes building a simple stack of form controls easy, 
>> and can also be used for advanced DialogBoxes.
>> 
>> Jeff Martin
>> 214.513.1636
>> 
>> 
>> On Jun 20, 2014, at 7:05 AM, Stephen 

hg: openjfx/8u-dev/rt: [SCENEBUILDER] Silence a compilation warning in sample code

[hang . vo]

Changeset: 84182535a4be
Author:yjoan
Date:  2014-06-20 17:12 +0200
URL:   http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/84182535a4be

[SCENEBUILDER] Silence a compilation warning in sample code

! 
apps/scenebuilder/samples/IssueTrackingLite/src/issuetrackinglite/model/TrackingServiceStub.java

Keyboard input testing report for 8u20

[Anthony Petrov]

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 languages.


MS Windows:
Everything works as expected. I've tested all known (to me) dead keys in 
all the keyboard layouts, and they produce expected results, allowing 
users to enter all the characters that they want.


Mac:
JavaFX supports international keyboard layouts on Mac somewhat poorly. 
Using dead keys on European keyboards may result in inserting two 
characters when only one is expected. On the bright side, though, JP 
input seems to work just fine. Also, it's a known issue (RT-35074) that 
OEM keys generate wrong key codes on Mac (but at least the keys generate 
correct characters which is actually more essential for text input). To 
sum it up: you can enter any characters you want, it's just that 
sometimes you have to hit Backspace or Delete here or there to remove 
some garbage.


Gtk:
Well, on Linux some work remains to be done, too. To be more precise, I 
wasn't able to use any dead keys at all, although "pre-accented" keys 
work just fine. I don't seem to be able to configure JP or CN input 
methods on my Linux, so I wasn't able to test the Asian kbd layouts.



I've filed a few JIRAs along my testing. I'll be working on polishing 
keyboard input support on Mac for 8u40. We'll do our best to support 
Linux/Gtk too, but realistically, I expect this to happen some time 
closer to FX 9 on that platform.


--
best regards,
Anthony

Re: Dialogs in JavaFX

[Stephen F Northover]

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 issues.  The downside is that 
JIRA does not provide threaded conversations and it can be hard to follow.


Steve

On 2014-06-20, 9:41 AM, Jeff Martin wrote:

That is a great post. I think the big problem with dialogs in Swing was the 
permutations problem. There were four basic types of dialogs (Message, Confirm, 
Option, Input) with six different parameters (Title, Message, Icon, Content, 
MessageType, Options) - so JOptionPane ended up with a sea of static methods 
that were confusing to navigate.

I don't think you could go wrong with a simple DialogBox class like this (I 
love simple):

// Constructor
public DialogBox(String aTitle);

// Options
public String getTitle();
public void setTitle(String aTitle);
public String getMessage();
public void setMessage(String aMessage);
public MessageType getMessageType();
public void setMessageType(MessageType aMessageType);
public Node getContent();
public void setContent(Node aNode);
public Node getGraphic();
public void setGraphic(Node aNode);
public String[] getOptions();
public void setOptions(String ... theOptions);

// Convenience methods to set Message + MessageType
public void setErrorMessage(String aMessage);
public void setWarningMessage(String aMessage);
public void setQuestionMessage(String aMessage);

// Show methods
public void showMessageDialog(T aComp);
public boolean showConfirmDialog(T aComp);
public int showOptionDialog(T aComp, String aDefault);
public String showInputDialog(T aComp, String aDefault);

// Programatic dismissal
public void confirm();
public void cancel();

Then most common invocations would look something like this:

// Get user confirmation
DialogBox dbox = new DialogBox("Sanity Check");
dbox.setWarningMessage("Are you sure you want to do this? It could kill 
you.");
if(!dbox.showConfirmationDialog(focusedNode)) return;

Using instance methods instead of static methods gives opportunity to subclass 
and override various methods. And notice the Content attribute - for the 
standard case when no Content is provided, it is built programmatically based 
on the parameters (essentially just the message and either an Option combo, an 
input textfield or nothing).

I've been using this in my JavaFX app for a while and it is working great and 
makes porting from Swing easy. I even built it on a convenient FormBuilder 
class that makes building a simple stack of form controls easy, and can also be 
used for advanced DialogBoxes.

Jeff Martin
214.513.1636


On Jun 20, 2014, at 7:05 AM, Stephen F Northover  
wrote:


Great post Jonathan.  The summary is that whatever direction we take, we'll 
have a plan for the future.  So if we run out of time and provide only a very 
scaled back API, we'll have prototyped how it can evolve to handle more complex 
cases.

Steve

On 2014-06-20, 12:37 AM, Jonathan Giles wrote:

Hi all,

Dialogs are something everyone wants, and also something most people seem to 
have an opinion on! JavaFX 8u40 will have dialogs, but what form they take 
(API-wise) is not yet defined. I've posted a relatively long discussion on this 
over at FX Experience [1] and your feedback is highly welcome. As I note in the 
blog post, the Jira issue for this feature is RT-12643. If you have any 
thoughts, please do post them there (rather than spam the many good people 
subscribed to openjfx-dev).

[1] http://fxexperience.com/2014/06/bringing-dialogs-to-javafx/

Thanks!

Re: Dialogs in JavaFX

[Jeff Martin]

That is a great post. I think the big problem with dialogs in Swing was the 
permutations problem. There were four basic types of dialogs (Message, Confirm, 
Option, Input) with six different parameters (Title, Message, Icon, Content, 
MessageType, Options) - so JOptionPane ended up with a sea of static methods 
that were confusing to navigate.

I don't think you could go wrong with a simple DialogBox class like this (I 
love simple):

// Constructor
public DialogBox(String aTitle);

// Options
public String getTitle();
public void setTitle(String aTitle);
public String getMessage();
public void setMessage(String aMessage);
public MessageType getMessageType();
public void setMessageType(MessageType aMessageType);
public Node getContent();
public void setContent(Node aNode);
public Node getGraphic();
public void setGraphic(Node aNode);
public String[] getOptions();
public void setOptions(String ... theOptions);

// Convenience methods to set Message + MessageType
public void setErrorMessage(String aMessage);
public void setWarningMessage(String aMessage);
public void setQuestionMessage(String aMessage);

// Show methods
public void showMessageDialog(T aComp);
public boolean showConfirmDialog(T aComp);
public int showOptionDialog(T aComp, String aDefault);
public String showInputDialog(T aComp, String aDefault);

// Programatic dismissal
public void confirm();
public void cancel();

Then most common invocations would look something like this:

// Get user confirmation
DialogBox dbox = new DialogBox("Sanity Check");
dbox.setWarningMessage("Are you sure you want to do this? It could kill 
you.");
if(!dbox.showConfirmationDialog(focusedNode)) return;

Using instance methods instead of static methods gives opportunity to subclass 
and override various methods. And notice the Content attribute - for the 
standard case when no Content is provided, it is built programmatically based 
on the parameters (essentially just the message and either an Option combo, an 
input textfield or nothing).

I've been using this in my JavaFX app for a while and it is working great and 
makes porting from Swing easy. I even built it on a convenient FormBuilder 
class that makes building a simple stack of form controls easy, and can also be 
used for advanced DialogBoxes.

Jeff Martin
214.513.1636


On Jun 20, 2014, at 7:05 AM, Stephen F Northover  
wrote:

> Great post Jonathan.  The summary is that whatever direction we take, we'll 
> have a plan for the future.  So if we run out of time and provide only a very 
> scaled back API, we'll have prototyped how it can evolve to handle more 
> complex cases.
> 
> Steve
> 
> On 2014-06-20, 12:37 AM, Jonathan Giles wrote:
>> Hi all,
>> 
>> Dialogs are something everyone wants, and also something most people seem to 
>> have an opinion on! JavaFX 8u40 will have dialogs, but what form they take 
>> (API-wise) is not yet defined. I've posted a relatively long discussion on 
>> this over at FX Experience [1] and your feedback is highly welcome. As I 
>> note in the blog post, the Jira issue for this feature is RT-12643. If you 
>> have any thoughts, please do post them there (rather than spam the many good 
>> people subscribed to openjfx-dev).
>> 
>> [1] http://fxexperience.com/2014/06/bringing-dialogs-to-javafx/
>> 
>> Thanks!
>> 
> 

Re: Testing accessibility / sample apps

[Stephen F Northover]

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 the 
best way to work with the team anyway because you can get fixes as they 
are made.  EA builds take a while to come out and there is no substitute 
for running on the latest code base.


Unfortunately due to Microsoft, building OpenJFX is a bit harder on 
Windows.  However, it is doable and the build instructions should be 
complete.  If they are not (and if you hit any problems), please post 
back to this list.


Here are the build instructions:

https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX

Many committers use an IDE (you don't have to) and OpenJFX is supports 
the three major IDE vendors:


https://wiki.openjdk.java.net/display/OpenJFX/Using+an+IDE

Looking forward to working with you,
Steve

On 2014-06-19, 7:10 PM, Felipe Heidrich wrote:

Hi Jann,

Unfortunately Linux support is not in the plan for 8u40.

Windows 7 is supported and we have recently fixed JAWS support (see 
https://javafx-jira.kenai.com/browse/RT-37530 and 
https://javafx-jira.kenai.com/browse/RT-37609).
Unfortunately due to the 8u20 to 8u40 transition the code has not being 
released yet, but soon.

The majority of our testing was done using Narrator. That said, I also tested 
NVDA lastest version on Windows 8 and I didn’t see any major problems.
On the Mac we tested with VoiceOver.

Regards,
Felipe


On Jun 19, 2014, at 2:24 PM, Jann Schneider  
wrote:


Hello all,

As a blind java developer i'm interessted in testing the accessibility of 
JavaFX and maybe help to find some issues.

I've just set up my build environment on my ubuntu 14.04 laptop and checked out 
the project files as described in the wiki. I could also set it up on a windows 
7 with Jaws 15 and NVDa (don't know what the current version is) for 
comparison..

No i am wondering if there are some examples i could try?

Regards Jann

Re: Dialogs in JavaFX

[Stephen F Northover]

Great post Jonathan.  The summary is that whatever direction we take, 
we'll have a plan for the future.  So if we run out of time and provide 
only a very scaled back API, we'll have prototyped how it can evolve to 
handle more complex cases.


Steve

On 2014-06-20, 12:37 AM, Jonathan Giles wrote:

Hi all,

Dialogs are something everyone wants, and also something most people 
seem to have an opinion on! JavaFX 8u40 will have dialogs, but what 
form they take (API-wise) is not yet defined. I've posted a relatively 
long discussion on this over at FX Experience [1] and your feedback is 
highly welcome. As I note in the blog post, the Jira issue for this 
feature is RT-12643. If you have any thoughts, please do post them 
there (rather than spam the many good people subscribed to openjfx-dev).


[1] http://fxexperience.com/2014/06/bringing-dialogs-to-javafx/

Thanks!

hg: openjfx/8u-dev/rt: RT-37254: Hook up SceneBuilder samples for building and later for supporting insanity testing

[hang . vo]

Changeset: b60bc59b09d1
Author:yjoan
Date:  2014-06-20 11:00 +0200
URL:   http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/b60bc59b09d1

RT-37254: Hook up SceneBuilder samples for building and later for supporting 
insanity testing
Summary: SceneBuilder samples are now compiled when "gradle apps" is called
Reviewed-by: ddhill, kcr
Contributed-by: ddhill

! apps/build.xml
+ apps/scenebuilder/build.xml
! apps/scenebuilder/samples/AirportApp/nbproject/project.properties
! apps/scenebuilder/samples/HelloI18N/nbproject/project.properties
! apps/scenebuilder/samples/HelloSwingNode/nbproject/project.properties
! apps/scenebuilder/samples/IssueTrackingBiDi/nbproject/project.properties
! apps/scenebuilder/samples/IssueTrackingLite/nbproject/project.properties
! apps/scenebuilder/samples/Login/nbproject/project.properties
! apps/scenebuilder/samples/UnlockCustom/nbproject/project.properties
+ apps/scenebuilder/samples/build.xml
! build.gradle