|
|
|
|
|
|
|
|
|
Re: e(fx)clipse not installing on Kepler for some reason. [message #1424858 is a reply to message #1424837] |
Tue, 16 September 2014 14:14 |
Thomas Schindl Messages: 6651 Registered: July 2009 |
Senior Member |
|
|
On 16.09.14 15:36, Joe Thatcher wrote:
> Thomas Schindl wrote on Tue, 16 September 2014 13:15
>> Ok - so you are on Java7. How did you create your project? On Java7 you
>> need to use the JavaFX Project Wizard because you are in need of an
>> extra classpath container.
>>
>> BTW: e(fx)clipse 1.0 requires Luna so it would not have worked for you
>> anyways
>> BTW2: JDK1.7.0_11 looks really old you should try upgrading to a newer
>> version if you do JavaFX-dev
>> BTW3: I strongly recommend to develop JavaFX apps with JDK8, JavaFX8 is
>> much more mature than JavaFX2.2 and you only get bugfixes for JavaFX8,
>> JavaFX2.2 only gets security fixes
>>
>> Tom
>>
>> On 16.09.14 14:56, Joe Thatcher wrote:
>> > Just managed to install it on Kepler, but the JavaFX imports are still
>> > not working.
>> > Screenshot: gyazo
>
> I am getting somewhat confused here.
>
> I installed with Kepler on version 0.9.0 which you said would work? Even
> though it isn't.
I only mentionned that you would have never been able to run e(fx)clipse
1.0 because the tooling uses Java8 features.
>
> Also, what about my players who use 1.6 java? Would my JavaFX
> applications still work for them? And what about 1.7?
The general answer to this question is that you are shipping the JRE
with your application, this is what the javafx-packager is doing for you.
JavaFX8 will only run on Java8.
If you want to stick with JavaFX2.2 (but note to yourself that I warned
you from using it for real world dev) so be it, e(fx)clipse 1.0 and
e(fx)clipse 0.9.0 happily support it (but e(fx)clipse 1.0 *as a tool*
needs to be running on JDK8) but once more I repeat - e(fx)clipse 0.9.0
is enough.
Create a project using our wizard and JavaFX imports will happily show up.
Tom
|
|
|
Powered by
FUDForum. Page generated in 0.04725 seconds