[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-03-19 Thread Shai Almog
No. This will take a while. The bottom line is that we need to rewrite the entire approach for packaging the application. That will take some time. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-03-19 Thread remonkroep
Any luck? -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to codenameone-discussions+unsubscr...@googlegroups.com. Visit this group at

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-03-14 Thread Shai Almog
Ugh. This is much harder than I feared. I've been banging my head against it and see no choice other than completely rewriting the desktop build process. That could take some time. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-03-14 Thread remonkroep
I used the build hint and when I look at the installed app inside the jfxswt.jar manifest.mf is see the following: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.9.2 Created-By: 1.8.0_40-b27 (Oracle Corporation) So It did not seem to update the JavaFX library. rt.jar manifest.mf:

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-03-13 Thread Shai Almog
On Mac this won't compile yet. As I mentioned this is a problem. On Windows just define the build hint, it should use the ZuluFX SDK instead of the default SDK. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-03-13 Thread remonkroep
Shai, How can I test the changes you made to make sure this fixes the issue? -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-03-13 Thread remonkroep
Shai, How can I test the changes you made to make sure this fixes the issue? On Tuesday, March 12, 2019 at 11:27:50 PM UTC-4, Shai Almog wrote: > > We're working on it but as suspected it's harder than just switching the > JDK implementation. > We added new build hints: > >

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-03-12 Thread Shai Almog
We're working on it but as suspected it's harder than just switching the JDK implementation. We added new build hints: win.desktop-vm=zuluFx8 mac.desktop-vm=zuluFx8 The Windows version seems to work. I haven't testing it other than checking that it compiled. The mac version doesn't seem to

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-03-12 Thread remonkroep
Any updates on this? -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to codenameone-discussions+unsubscr...@googlegroups.com. Visit this group at

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-02-22 Thread remonkroep
Early March would be fine. Thank you. On Thursday, February 21, 2019 at 10:51:47 PM UTC-5, Shai Almog wrote: > > I suggest following the blog as it's all announced there. We are currently > in code freeze which we entered on the 20th. It's for one week until the > 27th. > We can address this

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-02-21 Thread Shai Almog
I suggest following the blog as it's all announced there. We are currently in code freeze which we entered on the 20th. It's for one week until the 27th. We can address this early March. I think a better option would be something like https://www.azul.com/downloads/zulu/zulufx/ -- You

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-02-21 Thread remonkroep
Understood. When is the 6.0 release scheduled for? I hope you could please make the upgrade of the JVM to at least version 1.8.0_144 your number one priority after the release of 6.0, so this can be released as an interim release before 7.0 goes out. On Wednesday, February 20, 2019 at

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-02-20 Thread Shai Almog
The JVM works as it should. You are having an issue with a specific feature within the browser in JavaFX. You informed us of this issue at a point in time that's too close to the release cycle. To avoid risk that would impact all users of this feature this was postponed until after the

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-02-20 Thread remonkroep
Shai, I am running into issues where the javapackager builds the EXE however then when installing the EXE I get the following error: "Failed to find library: jvm.dll". The whole point of us using CN1 is to not have to look into these platform specific issues. Please upgrade your JDK to at

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-02-15 Thread Shai Almog
We use javafxpackager which was later renamed javapackager. It's available in the right click menu in the downloaded sources but you need some installs to get it working. Just google these to find the Oracle and 3rd party documentation -- You received this message because you are subscribed

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-02-15 Thread remonkroep
Do you have documentation on how to package locally? On Thursday, February 14, 2019 at 11:15:17 PM UTC-5, Shai Almog wrote: > > When I say version 7.0 it's a full timeline which starts in March and is > currently planned to end in June. It's not a specific date. We can try and > aim to an

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-02-14 Thread Shai Almog
When I say version 7.0 it's a full timeline which starts in March and is currently planned to end in June. It's not a specific date. We can try and aim to an earlier stage in the cycle but make sure to remind us. We won't make a change to server setup this close to the release. Past experience

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-02-14 Thread remonkroep
Shai, When is the 7.0 release planned for? Could you at least upgrade to JVM version 1.8.0_144-b01 or higher in the meantime since I need this in our production environment as soon as possible. On Wednesday, February 13, 2019 at 10:20:03 PM UTC-5, Shai Almog wrote: > > The desktop build

[codenameone-discussions] Re: JavaFX used by Windows and Mac OS Desktop builds outdated.

2019-02-13 Thread Shai Almog
The desktop build uses a JDK that's packaged in the install. We need to update it but ideally we'd want to go to something much newer e.g. OpenJDK 11 with the new AoT compiler. The challenge here is preventing the newer JDK from conflicting with older code we have on the servers so this isn't