Keep using the version of Netbeans you are using. There's no "rush" for
you to upgrade.
That said, however, the "rush" to get off JDK 8 is speed and features. JDK
8 is not capable of many of the current features of JDK 21. To expect the
developers to remain stuck in past decades and to not use
Niel's proposal is at least 3 years over due. What needs to be remembered
is that Netbeans does not time-outthe license does not expire, etc.
People who need to work with JDK8 can do so into eternity by keeping a JDK8
version of netbeans. This machine I am writing on has 11 versions of
at 7:41 AM Matthias Bläsing
wrote:
> Hi Chuck,
>
> Am Freitag, dem 21.01.2022 um 06:46 -0800 schrieb Chuck Davis:
> > Am I the only one who wants to create a Java class library with
> > Maven?
> > I see it can be done with Ant or Gradle but not Mavenstill.
>
> what
Am I the only one who wants to create a Java class library with Maven? I
see it can be done with Ant or Gradle but not Mavenstill.
My only experience with Gradle is with Android Studio and it (Studio with
Gradle/Kotlin) is a disaster area. I hope we're not headed that direction.
On Fri,
A decision long over-due.
On Wed, Feb 26, 2020 at 5:13 PM Laszlo Kishalmi
wrote:
> Dear all,
>
> What do you think about stopping support Java 8 as NetBeans runtime from
> 12.1 and on?
>
> Neil mentioned it in the user's chat first regarding that we have issues
> with nb-javac from time to
I KNEW if I touched it I would blow up the whole thing. I looked at the
page to see it it had changed this a.m. It changed alright but not for the
better I fear.
It seriously needs your attention (spell that "fix") again, Geertjan! Or
somebody else who knows what they're doing. I don't see
:
> Can you point to the page where you would like the YouTube clip to be
> listed?
>
> As you do that, notice the link at the bottom of the page for getting to
> the source of the page. Then edit the page online and prove your PR.
>
> Gj
>
> On Sat, 15 Feb 2020 a
t;
> On Sat, 15 Feb 2020 at 23:37, Chuck Davis wrote:
>
> > Geertjan, why not put a link to that on the netbeans page as a JFX
> > tutorial? That would save a number of people a lot of time searching for
> > help.
> >
> > On Sat, Feb 15, 2020 at 1:
15 Feb 2020 at 22:43, Neil C Smith wrote:
>
> > On Sat, 15 Feb 2020 at 21:27, Chuck Davis wrote:
> > > Neil, can you provide a link or a description how to get to the #3 you
> > > mention? I think you're referencing some resource about which I'm
> > ignorant
Oh, ok. Thanks. They aren't numbered so I got confused.
On Sat, Feb 15, 2020 at 1:43 PM Neil C Smith wrote:
> On Sat, 15 Feb 2020 at 21:27, Chuck Davis wrote:
> > Neil, can you provide a link or a description how to get to the #3 you
> > mention? I think you're referencin
Neil, can you provide a link or a description how to get to the #3 you
mention? I think you're referencing some resource about which I'm ignorant
at the moment. Thanks.
>
> With the Maven archetypes, while it's somewhat annoying it doesn't
> work with the default run action, it's only a case
I think this is a much better resource for JavaFX.
https://openjfx.io/openjfx-docs/
It would also be nice to have a tutorial @ netbeans.apache.org in the
"learn" section. Netbeans can, at last, create a FX project that
compiles. It does not yet create an environment that will "run" it by
We're talking about very, VERY subjective perspectives here. Just because
there is a new fad called "flat" doesn't mean it's an improvement.
Actually, "flat" looks so 1970's ish. Perhaps the fascination with it is
due to the fact that most of the productive people here either weren't
alive at
Well put, Scott.
I have used quite a few web applications. They all suck. Either a browser
cannot provide a decent interface for applications or nobody has yet
figured out how to do it. Browsers are great for displaying information
and downloading files but they are a reprehensible invention
I can't recall if this worked differently before but I think it did.
If I refactor a class by moving from one package to another it does not
update the package definition within the class. It does highlight it as an
error and the fix is on the pop-up menu but I thought refactoring did that
Thanks for the explanation, Matthias. JavaFX appears to make adding help
to an application quite simple -- when I get to that phase.
On Tue, Oct 1, 2019 at 10:12 AM Matthias Bläsing
wrote:
> Hi Chuck,
>
> Am Sonntag, den 29.09.2019, 04:34 -0700 schrieb Chuck Davis:
> > Matthi
Hi Scott:
I responded off-list as well since this is a bit off topic.
I was just wondering how using HTML in JFX was working for Matthias since
we no longer have JavaHelp available to NB development.
Yes, using JFX in NB development is quite nice. Getting it to run outside
the IDE is another
Matthias, is your use case possibly displaying help for your application?
I ask because I'm thinking of attempting this in my app. The "modern"
approach to have help in an external browser is really, really annoying.
P. S. It's really easy to develop with JFX (and getting better).
Well, everything got screwed-up between JDK8 and JDK9++, Patrick. I'm not
always sure the "progress" was progress. It would certainly be nice if FX
were still part of the JDK.
Here's hoping WorkbenchFX works for you.
On Sun, Sep 29, 2019 at 1:31 AM Patrik Karlström wrote:
> Thanks for your
Partick,
I've been waiting for somebody more knowledgeable to speak up but here
goes. Based on previous conversations on this list and elsewhere, there is
not going to be a JFX based NB WindowManager anytime soon. Experiments
have been done but the effort is exhaustive. If you need JFX in a
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
21 matches
Mail list logo
