You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Geertjan Wielenga <ge...@apache.org> on 2019/08/25 09:42:15 UTC
What to do with JavaFX and OpenJFX?
Hi all,
What to do with JavaFX and OpenJFX?
Should we continue making projects and samples available for JDK 8 JavaFX
in the New Project dialog, because some users may be using JDK 8, or should
we only have projects and samples for OpenJFX in the New Project dialog?
The full situation is described in detail here in a new blog entry I wrote
a few minutes ago:
https://blogs.apache.org/netbeans/entry/what-to-do-with-javafx
Thanks,
Gj
Re: Re: What to do with JavaFX and OpenJFX?
Posted by Eric Bresie <eb...@gmail.com>.
In a sense isn’t this really a flavor of incompatible libraries? Say for example junit 3/4/5 with each needing separate instances of the dependencies being defined and added in some way?
Or maybe should ask how was it handle switching from JavaFX 1(JavaFX script version) vs JavaFX 2 (redone was java based versions) previously?
Given the recent different java EE in play maybe something similar there with new/legacy/version specific.
Can always mark some elements as @depricated to provide some time to prune eventually.
Could some form of hint/tip be added towards migration to openjfx version sort of like some places where new java features are suggested like string/expression case statements, diamond operators, lambdas, etc.?
Heh...at some point is the Netbeans UI going to be redone in jfx ;-) ?
Eric Bresie
Ebresie@gmail.com
> On August 25, 2019 at 10:28:31 AM CDT, Vlad Palnik <vl...@gmail.com> wrote:
> NetBeans needs to support any Java version that has not reached EOL. Most
> production environments use LTS versions and as long as they are are
> supported by Oracle they need to be supported by NB.
>
> On Sun, Aug 25, 2019, 8:21 AM Chuck Davis <cj...@gmail.com> wrote:
>
> > At the pace Java is moving no reasonable person would expect ANYTHING based
> > upon Java to forever be backwardly compatible.
> >
> > In my not so humble opinion we need a clean break occasionally where we say
> > the current Java environment requires new capabilities in the IDE and
> > version x.x will no longer work on Java versions less than x.x.
> >
> > For people still stuck on Java8 they should be able to indefinitely work
> > with Netbeans 11.1 and lower. For people progressing with newer versions
> > of Java (my Linux distro keeps Java up to date automatically) the IDE needs
> > to drop old features and add new Java features as Java changes. It's going
> > to require backward compatibility to be broken but that does not mean the
> > version that worked at that version of Java should be discontinued at least
> > for a number of years -- it should still be available to those working with
> > older versions of Java. Enterprises update much more slowly than the Java
> > world progresses.
> >
> > So I vote for NB 12 to drop support for Java 11 and lower to concentrate on
> > incorporating the new features of Java and not be hassled by backward
> > compatibility. Those still on Java 11 and below can happily keep on using
> > NB 11.1 indefinitely.
> >
> > Just my $.02 and I am well aware it is a minority opinion.
> >
> > On Sun, Aug 25, 2019 at 2:42 AM Geertjan Wielenga <ge...@apache.org>
> > wrote:
> >
> > > Hi all,
> > >
> > > What to do with JavaFX and OpenJFX?
> > >
> > > Should we continue making projects and samples available for JDK 8 JavaFX
> > > in the New Project dialog, because some users may be using JDK 8, or
> > should
> > > we only have projects and samples for OpenJFX in the New Project dialog?
> > >
> > > The full situation is described in detail here in a new blog entry I
> > wrote
> > > a few minutes ago:
> > >
> > > https://blogs.apache.org/netbeans/entry/what-to-do-with-javafx
> > >
> > > Thanks,
> > >
> > > Gj
> > >
> >
Re: What to do with JavaFX and OpenJFX?
Posted by Vlad Palnik <vl...@gmail.com>.
NetBeans needs to support any Java version that has not reached EOL. Most
production environments use LTS versions and as long as they are are
supported by Oracle they need to be supported by NB.
On Sun, Aug 25, 2019, 8:21 AM Chuck Davis <cj...@gmail.com> wrote:
> At the pace Java is moving no reasonable person would expect ANYTHING based
> upon Java to forever be backwardly compatible.
>
> In my not so humble opinion we need a clean break occasionally where we say
> the current Java environment requires new capabilities in the IDE and
> version x.x will no longer work on Java versions less than x.x.
>
> For people still stuck on Java8 they should be able to indefinitely work
> with Netbeans 11.1 and lower. For people progressing with newer versions
> of Java (my Linux distro keeps Java up to date automatically) the IDE needs
> to drop old features and add new Java features as Java changes. It's going
> to require backward compatibility to be broken but that does not mean the
> version that worked at that version of Java should be discontinued at least
> for a number of years -- it should still be available to those working with
> older versions of Java. Enterprises update much more slowly than the Java
> world progresses.
>
> So I vote for NB 12 to drop support for Java 11 and lower to concentrate on
> incorporating the new features of Java and not be hassled by backward
> compatibility. Those still on Java 11 and below can happily keep on using
> NB 11.1 indefinitely.
>
> Just my $.02 and I am well aware it is a minority opinion.
>
> On Sun, Aug 25, 2019 at 2:42 AM Geertjan Wielenga <ge...@apache.org>
> wrote:
>
> > Hi all,
> >
> > What to do with JavaFX and OpenJFX?
> >
> > Should we continue making projects and samples available for JDK 8 JavaFX
> > in the New Project dialog, because some users may be using JDK 8, or
> should
> > we only have projects and samples for OpenJFX in the New Project dialog?
> >
> > The full situation is described in detail here in a new blog entry I
> wrote
> > a few minutes ago:
> >
> > https://blogs.apache.org/netbeans/entry/what-to-do-with-javafx
> >
> > Thanks,
> >
> > Gj
> >
>
Re: What to do with JavaFX and OpenJFX?
Posted by Neil C Smith <ne...@apache.org>.
On Mon, 26 Aug 2019, 01:11 Eirik Bakke, <eb...@ultorg.com> wrote:
> > So I vote for NB 12 to drop support for Java 11
>
> Java 11 was released less than a year ago... _way_ too early to stop
> supporting.
>
Too right! There's an open bug report that we accidentally dropped Java 7
support in 11.1, which I think is fixed in 11.2. In my opinion we should
aim to always support current and previous Java LTS as a baseline, so 8 and
11 for the foreseeable. Unless we actively want to whittle down the user
base?! And we should not encourage anyone to stick on our older,
particularly non-LTS, releases either. Nor drop features in an LTS release.
On JavaFX though, I'd suggest adding the revised OpenJFX archetype
templates in 11.2, and give serious consideration to dropping most of the
legacy JavaFX stuff in 11.3 (prior to next LTS, but not rushed now?). Could
look to stagger to ensure people can work with existing legacy projects for
a while longer? Could also hide/rename/remove samples now I guess?
Best wishes,
Neil
RE: What to do with JavaFX and OpenJFX?
Posted by Eirik Bakke <eb...@ultorg.com>.
> So I vote for NB 12 to drop support for Java 11
Java 11 was released less than a year ago... _way_ too early to stop supporting. New Java versions often introduce new bugs in various areas, which prevent upgrading every application on every release. "If it ain't broken, don't fix it."
For example, Java 9 introduced a performance bug that made LineBreakMeasurer ten times slower than in Java 8 [1]. In Java 9 this could be worked around with a command line option, but that option disappeared in Java 10. The final bugfix was made in Java 13. So for my own app in particular, it was quite sensible to "sit out" Java 10, 11, and 12.
And NetBeans itself still uses Java 8 for its own build environment. It would be sad not to be able to develop NetBeans on NetBeans...
(IntelliJ, as another example, is itself still running on JDK8.)
-- Eirik
[1] https://bugs.openjdk.java.net/browse/JDK-8202131
-----Original Message-----
From: Chuck Davis <cj...@gmail.com>
Sent: Sunday, August 25, 2019 11:22 AM
To: dev@netbeans.apache.org
Subject: Re: What to do with JavaFX and OpenJFX?
At the pace Java is moving no reasonable person would expect ANYTHING based upon Java to forever be backwardly compatible.
In my not so humble opinion we need a clean break occasionally where we say the current Java environment requires new capabilities in the IDE and version x.x will no longer work on Java versions less than x.x.
For people still stuck on Java8 they should be able to indefinitely work with Netbeans 11.1 and lower. For people progressing with newer versions of Java (my Linux distro keeps Java up to date automatically) the IDE needs to drop old features and add new Java features as Java changes. It's going to require backward compatibility to be broken but that does not mean the version that worked at that version of Java should be discontinued at least for a number of years -- it should still be available to those working with older versions of Java. Enterprises update much more slowly than the Java world progresses.
So I vote for NB 12 to drop support for Java 11 and lower to concentrate on incorporating the new features of Java and not be hassled by backward compatibility. Those still on Java 11 and below can happily keep on using NB 11.1 indefinitely.
Just my $.02 and I am well aware it is a minority opinion.
On Sun, Aug 25, 2019 at 2:42 AM Geertjan Wielenga <ge...@apache.org>
wrote:
> Hi all,
>
> What to do with JavaFX and OpenJFX?
>
> Should we continue making projects and samples available for JDK 8
> JavaFX in the New Project dialog, because some users may be using JDK
> 8, or should we only have projects and samples for OpenJFX in the New Project dialog?
>
> The full situation is described in detail here in a new blog entry I
> wrote a few minutes ago:
>
> https://blogs.apache.org/netbeans/entry/what-to-do-with-javafx
>
> Thanks,
>
> Gj
>
Re: What to do with JavaFX and OpenJFX?
Posted by Chuck Davis <cj...@gmail.com>.
At the pace Java is moving no reasonable person would expect ANYTHING based
upon Java to forever be backwardly compatible.
In my not so humble opinion we need a clean break occasionally where we say
the current Java environment requires new capabilities in the IDE and
version x.x will no longer work on Java versions less than x.x.
For people still stuck on Java8 they should be able to indefinitely work
with Netbeans 11.1 and lower. For people progressing with newer versions
of Java (my Linux distro keeps Java up to date automatically) the IDE needs
to drop old features and add new Java features as Java changes. It's going
to require backward compatibility to be broken but that does not mean the
version that worked at that version of Java should be discontinued at least
for a number of years -- it should still be available to those working with
older versions of Java. Enterprises update much more slowly than the Java
world progresses.
So I vote for NB 12 to drop support for Java 11 and lower to concentrate on
incorporating the new features of Java and not be hassled by backward
compatibility. Those still on Java 11 and below can happily keep on using
NB 11.1 indefinitely.
Just my $.02 and I am well aware it is a minority opinion.
On Sun, Aug 25, 2019 at 2:42 AM Geertjan Wielenga <ge...@apache.org>
wrote:
> Hi all,
>
> What to do with JavaFX and OpenJFX?
>
> Should we continue making projects and samples available for JDK 8 JavaFX
> in the New Project dialog, because some users may be using JDK 8, or should
> we only have projects and samples for OpenJFX in the New Project dialog?
>
> The full situation is described in detail here in a new blog entry I wrote
> a few minutes ago:
>
> https://blogs.apache.org/netbeans/entry/what-to-do-with-javafx
>
> Thanks,
>
> Gj
>
Re: What to do with JavaFX and OpenJFX?
Posted by Emilian Bold <em...@gmail.com>.
Note that you could still have a modern JDK with JavaFX, eg.
https://www.azul.com/downloads/zulu-community/?&version=java-11-lts&os=macos&architecture=x86-64-bit&package=jdk-fx
I had to use it this year as it was the simplest way of getting some
JavaFX project to run.
Sounds to me that OpenFX would go hand in hand with a switch to Maven?
Existing JavaFX / Platform apps could be ant-based and it's there's
any build.xml customisation (and you know there will be) then the
Maven switch will be non-trivial.
So the question should not be how to notify users about OpenFX but how
to help them on this migration path. Which, of course, it's much more
work.
My 2c,
--emi
On Sun, Aug 25, 2019 at 12:42 PM Geertjan Wielenga <ge...@apache.org> wrote:
>
> Hi all,
>
> What to do with JavaFX and OpenJFX?
>
> Should we continue making projects and samples available for JDK 8 JavaFX
> in the New Project dialog, because some users may be using JDK 8, or should
> we only have projects and samples for OpenJFX in the New Project dialog?
>
> The full situation is described in detail here in a new blog entry I wrote
> a few minutes ago:
>
> https://blogs.apache.org/netbeans/entry/what-to-do-with-javafx
>
> Thanks,
>
> Gj
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: What to do with JavaFX and OpenJFX?
Posted by Geertjan Wielenga <ge...@apache.org>.
That makes sense — the lines to include that module have not yet been put
into master, and now probably won’t be because we’ll be registering the
openjfx.io samples in a different and better way.
Gj
On Tue, 27 Aug 2019 at 16:19, Glenn Holmer <ce...@kolabnow.com.invalid>
wrote:
> On 8/27/19 8:02 AM, Sean M Phillips wrote:
> >>>> It works out of the box.
>
> > True... as of right now it successfully allows you to clean and build the
> > app. However this was not the case until recently. The default setup is
> > still missing aspects that would allow you to debug out of the box etc.
>
> For me (NetBeans 11.1, Java 11.0.4), the HelloFXWithMaven works
> (including debugging), but debugging HelloFXMLWithMaven fails with:
>
> Error: Could not find or load main class org.openjfxml.hellofx.App in
> module org.openjfx.hellofxml
>
> the reason being that line 71 of the POM should read
>
> <mainClass>org.openjfx.hellofxml/org.openjfx.hellofxml.App</mainClass>
>
> rather than
>
> <mainClass>org.openjfx.hellofxml/org.openjfxml.hellofx.App</mainClass>
>
> which looks like just a simple typo. I built NetBeans from source to fix
> it, but no longer see OpenJFX under Samples. Don't know what I did wrong
> there.
>
> --
> Glenn Holmer (Linux registered user #16682)
> "After the vintage season came the aftermath -- and Cenbe."
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
Re: What to do with JavaFX and OpenJFX?
Posted by Glenn Holmer <ce...@kolabnow.com.INVALID>.
On 8/27/19 8:02 AM, Sean M Phillips wrote:
>>>> It works out of the box.
> True... as of right now it successfully allows you to clean and build the
> app. However this was not the case until recently. The default setup is
> still missing aspects that would allow you to debug out of the box etc.
For me (NetBeans 11.1, Java 11.0.4), the HelloFXWithMaven works
(including debugging), but debugging HelloFXMLWithMaven fails with:
Error: Could not find or load main class org.openjfxml.hellofx.App in
module org.openjfx.hellofxml
the reason being that line 71 of the POM should read
<mainClass>org.openjfx.hellofxml/org.openjfx.hellofxml.App</mainClass>
rather than
<mainClass>org.openjfx.hellofxml/org.openjfxml.hellofx.App</mainClass>
which looks like just a simple typo. I built NetBeans from source to fix
it, but no longer see OpenJFX under Samples. Don't know what I did wrong
there.
--
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."
Re: What to do with JavaFX and OpenJFX?
Posted by Sean M Phillips <se...@gmail.com>.
Let me say for the record that I would prefer NetBeans to default to
OpenJFX 11 or higher etc. I like anything we can do to encourage users to
migrate from 8.
However I believe dropping support for JavaFX 8 at this time would be a bad
choice.
>>> It works out of the box.
True... as of right now it successfully allows you to clean and build the
app. However this was not the case until recently. The default setup is
still missing aspects that would allow you to debug out of the box etc. My
concern regarding the original question of this thread is that for many
people using Java and JavaFX 8 in production, they are unsure if NetBeans
11.x is ready. They have yet to see a functioning example in NetBeans. I
believe these users simply need "a little more time" to be comfortable with
the transition, say 6 months or another minor release cycle.
If support for JavaFX 8 were to be dropped right now, I fear a lot of these
users would simply switch to intelliJ. Developers are a fickle bunch... I
have some on my team that use intellij for our JavaFX apps simply because
it works and they heard it was a good IDE. No other reason.
Sean
On Tue, Aug 27, 2019 at 12:09 AM Geertjan Wielenga <ge...@apache.org>
wrote:
> It works out of the box. It is the openjfx.io POMs, e.g, this one:
>
>
> https://github.com/openjfx/samples/blob/master/HelloFX/Maven/hellofx/pom.xml
>
> It would be great if you'd open an issue and then specify what exactly
> needs to be in the POM for you, so that we can put it there for you so that
> it will not be incomplete.
>
> https://issues.apache.org/jira/projects/NETBEANS
>
> Above is where you can now please, file an issue. Provide there the POM
> that you would like to have. Can you do it, please?
>
> Gj
>
> On Tue, Aug 27, 2019 at 1:47 AM Kenneth Fogel <kf...@dawsoncollege.qc.ca>
> wrote:
>
> > I think its worth keeping support for the old JavaFX that shipped in 8
> > thru 10 (I think it ended at 10). However it should not be the default. I
> > was initially annoyed that there is not an updated pom.xml for OpenFX.
> > Geertjan pointed out that there is an OpenFX project in the Samples group
> > but its pom.xml appears incomplete. We could really use a flying squad
> that
> > examines every pom file that NetBeans adds to a project. They don't need
> to
> > be complex but there are certain plugins, i.e. Surefire, certain
> > dependencies in some cases, and certain goals that should be present. The
> > archetypes also need to be reviewed, I believe many are out of date.
> >
> > As for a quick fix, only have JavaFX as a choice under Ant if the default
> > JDK is 8. The Maven and Graddle choices should only have OpenFX but have
> a
> > sample JavaFX project in the Samples essentially reversing the current
> > setup..
> >
> > Ken
> >
> > PS: By suggesting such an overhaul I am willing to work on it.
> >
> >
> >
> > -----Original Message-----
> > From: Geertjan Wielenga <ge...@apache.org>
> > Sent: August 25, 2019 5:42 AM
> > To: dev <de...@netbeans.apache.org>
> > Subject: What to do with JavaFX and OpenJFX?
> >
> > Hi all,
> >
> > What to do with JavaFX and OpenJFX?
> >
> > Should we continue making projects and samples available for JDK 8 JavaFX
> > in the New Project dialog, because some users may be using JDK 8, or
> should
> > we only have projects and samples for OpenJFX in the New Project dialog?
> >
> > The full situation is described in detail here in a new blog entry I
> wrote
> > a few minutes ago:
> >
> > https://blogs.apache.org/netbeans/entry/what-to-do-with-javafx
> >
> > Thanks,
> >
> > Gj
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
Re: What to do with JavaFX and OpenJFX?
Posted by Geertjan Wielenga <ge...@apache.org>.
It works out of the box. It is the openjfx.io POMs, e.g, this one:
https://github.com/openjfx/samples/blob/master/HelloFX/Maven/hellofx/pom.xml
It would be great if you'd open an issue and then specify what exactly
needs to be in the POM for you, so that we can put it there for you so that
it will not be incomplete.
https://issues.apache.org/jira/projects/NETBEANS
Above is where you can now please, file an issue. Provide there the POM
that you would like to have. Can you do it, please?
Gj
On Tue, Aug 27, 2019 at 1:47 AM Kenneth Fogel <kf...@dawsoncollege.qc.ca>
wrote:
> I think its worth keeping support for the old JavaFX that shipped in 8
> thru 10 (I think it ended at 10). However it should not be the default. I
> was initially annoyed that there is not an updated pom.xml for OpenFX.
> Geertjan pointed out that there is an OpenFX project in the Samples group
> but its pom.xml appears incomplete. We could really use a flying squad that
> examines every pom file that NetBeans adds to a project. They don't need to
> be complex but there are certain plugins, i.e. Surefire, certain
> dependencies in some cases, and certain goals that should be present. The
> archetypes also need to be reviewed, I believe many are out of date.
>
> As for a quick fix, only have JavaFX as a choice under Ant if the default
> JDK is 8. The Maven and Graddle choices should only have OpenFX but have a
> sample JavaFX project in the Samples essentially reversing the current
> setup..
>
> Ken
>
> PS: By suggesting such an overhaul I am willing to work on it.
>
>
>
> -----Original Message-----
> From: Geertjan Wielenga <ge...@apache.org>
> Sent: August 25, 2019 5:42 AM
> To: dev <de...@netbeans.apache.org>
> Subject: What to do with JavaFX and OpenJFX?
>
> Hi all,
>
> What to do with JavaFX and OpenJFX?
>
> Should we continue making projects and samples available for JDK 8 JavaFX
> in the New Project dialog, because some users may be using JDK 8, or should
> we only have projects and samples for OpenJFX in the New Project dialog?
>
> The full situation is described in detail here in a new blog entry I wrote
> a few minutes ago:
>
> https://blogs.apache.org/netbeans/entry/what-to-do-with-javafx
>
> Thanks,
>
> Gj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
RE: What to do with JavaFX and OpenJFX?
Posted by Kenneth Fogel <kf...@dawsoncollege.qc.ca>.
I think its worth keeping support for the old JavaFX that shipped in 8 thru 10 (I think it ended at 10). However it should not be the default. I was initially annoyed that there is not an updated pom.xml for OpenFX. Geertjan pointed out that there is an OpenFX project in the Samples group but its pom.xml appears incomplete. We could really use a flying squad that examines every pom file that NetBeans adds to a project. They don't need to be complex but there are certain plugins, i.e. Surefire, certain dependencies in some cases, and certain goals that should be present. The archetypes also need to be reviewed, I believe many are out of date.
As for a quick fix, only have JavaFX as a choice under Ant if the default JDK is 8. The Maven and Graddle choices should only have OpenFX but have a sample JavaFX project in the Samples essentially reversing the current setup..
Ken
PS: By suggesting such an overhaul I am willing to work on it.
-----Original Message-----
From: Geertjan Wielenga <ge...@apache.org>
Sent: August 25, 2019 5:42 AM
To: dev <de...@netbeans.apache.org>
Subject: What to do with JavaFX and OpenJFX?
Hi all,
What to do with JavaFX and OpenJFX?
Should we continue making projects and samples available for JDK 8 JavaFX in the New Project dialog, because some users may be using JDK 8, or should we only have projects and samples for OpenJFX in the New Project dialog?
The full situation is described in detail here in a new blog entry I wrote a few minutes ago:
https://blogs.apache.org/netbeans/entry/what-to-do-with-javafx
Thanks,
Gj
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists