Re: [platform] Adding the WindowManager to a SwingNode

I managed to get hold of the org.netbeans.core.windows.view.ui.MainWindow and put it in a JavaFx Stage, however, much of the behavior got lost in the process so I guess this isn't the way to go. My little test is available at

Re: Question on Netbeans 11 and C++

Ah yes, MinGW, I remember now. It would have been a lot more overhead than Cygwin and at the time I just wanted to do a few simple command line applications. I was thinking about native Windows applications but I didn't get past the research stage. Thank you very much for elaborating. On Fri,

Re: Question on Netbeans 11 and C++

The other option is MinGW, both it and Cygwin are *NEVER* used by professional developers on Windows. They don’t work with the Windows SDK but instead attempt to supply their own version of Windows header files. Both options rely on awkward hacks to make Windows appear to have some more

Re: Hopefully close to the finish line with Java 11 & FX

This is a good first step. I think some rough edges remain though. For example, if you go to the project properties ->Build->Compile and flip the JDK between Java from 8 to 11+, I’m guessing everything breaks. Can we do anything helpful in that situation? JavaFX 13 requires Java 11. What

Re: Question on Netbeans 11 and C++

Scott wrote: > Existing NetBeans C/C++ support on Windows is not very practical. Bordering on almost unusable actually. (It requires use of a toolset that is virtually never used on Windows for native development, is incompatible with Windows SDKs, and difficult to maintain and configure.) For

Re: Hopefully close to the finish line with Java 11 & FX

Done. On Fri, Sep 27, 2019 at 8:09 AM Geertjan Wielenga wrote: > Also, please comment your support for this PR, which updates the Maven > plugin for OpenJFX to support both JDK 8 and beyond: > > https://github.com/openjfx/javafx-maven-plugin/pull/44 > > Gj > > >

Re: Hopefully close to the finish line with Java 11 & FX

Also, please comment your support for this PR, which updates the Maven plugin for OpenJFX to support both JDK 8 and beyond: https://github.com/openjfx/javafx-maven-plugin/pull/44 Gj On Fri, Sep 27, 2019 at 3:30 PM Geertjan Wielenga wrote: > > On Fri, Sep 27, 2019 at 3:27 PM Chuck Davis

Re: Hopefully close to the finish line with Java 11 & FX

On Fri, Sep 27, 2019 at 3:27 PM Chuck Davis wrote: > I think that is a fabulous idea I've been advocating for since JDK11 was > released. What is on the "create a new project" menu needs to create a > project that will build and run in the IDE. > There is a very simple way to advocate anything

Re: Hopefully close to the finish line with Java 11 & FX

I think that is a fabulous idea I've been advocating for since JDK11 was released. What is on the "create a new project" menu needs to create a project that will build and run in the IDE. On Fri, Sep 27, 2019 at 7:24 AM Geertjan Wielenga wrote: > > On Fri, Sep 27, 2019 at 3:21 PM Chuck Davis

Re: Hopefully close to the finish line with Java 11 & FX

Using NetBeans 11.2-beta1… Immediately after creating a new Maven JavaFX project the project shows errors. All imports from javafx.* are indicated as errors with the message “package does not exist” Building the project also fails with the bizarre error "Fatal Error: Unable to find package

Re: Hopefully close to the finish line with Java 11 & FX

On Fri, Sep 27, 2019 at 3:24 PM Chuck Davis wrote: > If using a "sample" is required that should be indicated someplace where > users will find it a project creation time. I've been using NB for many > years and have never had to resort to using a sample to create a project. > It's not what a

Re: Hopefully close to the finish line with Java 11 & FX

If using a "sample" is required that should be indicated someplace where users will find it a project creation time. I've been using NB for many years and have never had to resort to using a sample to create a project. It's not what a user would expect in my opinion. If NB wants to maintain

Re: Hopefully close to the finish line with Java 11 & FX

On Fri, Sep 27, 2019 at 3:21 PM Chuck Davis wrote: > I don't know what archetype should be "registered". I just know what > we've got doesn't work as expected by users. > Great. So let's fix it. The idea would be to remove the "JavaFX Application" that is currently there and causing you so

Re: Hopefully close to the finish line with Java 11 & FX

https://issues.apache.org/jira/browse/NETBEANS-3175 https://github.com/apache/netbeans/pull/1535 Gj On Fri, Sep 27, 2019 at 3:18 PM Geertjan Wielenga wrote: > Let's start by being clear about what this means: "Immediately after > creating a new Maven JavaFX project the project shows errors."

Re: Hopefully close to the finish line with Java 11 & FX

I don't know what archetype should be "registered". I just know what we've got doesn't work as expected by users. On Fri, Sep 27, 2019 at 7:13 AM Geertjan Wielenga wrote: > Here is where that archetype is registered, is there another one we should > register instead: > > >

Re: Hopefully close to the finish line with Java 11 & FX

Let's start by being clear about what this means: "Immediately after creating a new Maven JavaFX project the project shows errors." Can you just do step by step what you're doing, please? Ideally, use the Gluon OpenJFX samples in the Sample category in the New Project dialog -- and maybe we

Re: Hopefully close to the finish line with Java 11 & FX

Here is where that archetype is registered, is there another one we should register instead: https://github.com/apache/netbeans/blob/master/java/maven/src/org/netbeans/modules/maven/newproject/MavenWizardIterator.java See line 76 to 80 in the above. Gj On Fri, Sep 27, 2019 at 3:10 PM Chuck

Re: Hopefully close to the finish line with Java 11 & FX

I don't think most users are going to build a project from samples (they expect what's on the menu to work). Fortunately, I cared enough to find work-arounds people had posted on the internet but for new users it's a bombshell. On Fri, Sep 27, 2019 at 7:07 AM Geertjan Wielenga wrote: > Go to

Re: Hopefully close to the finish line with Java 11 & FX

Go to the Samples category in the New Project dialog and choose JavaFX. Gj On Fri, Sep 27, 2019 at 3:04 PM Chuck Davis wrote: > That would be a good motive to move to Gradle!! > > On Fri, Sep 27, 2019 at 7:00 AM Scott Palmer wrote: > >> You can also easily make a JavaFX project with NetBeans

Re: Hopefully close to the finish line with Java 11 & FX

That would be a good motive to move to Gradle!! On Fri, Sep 27, 2019 at 7:00 AM Scott Palmer wrote: > You can also easily make a JavaFX project with NetBeans if you use a > Gradle project - as everyone should ;-) > > https://openjfx.io/openjfx-docs/#gradle > > But you do have to manually add

Re: Hopefully close to the finish line with Java 11 & FX

I should have added "that compiles" under JDK 12. It may still work with JDK 8 -- don't know. On Fri, Sep 27, 2019 at 7:00 AM Chuck Davis wrote: > I just tried it a few minutes ago to be sure it hadn't been fixed. NB > 11.1 does NOT create a JFX application that compiles. > > >

Re: Hopefully close to the finish line with Java 11 & FX

I just tried it a few minutes ago to be sure it hadn't been fixed. NB 11.1 does NOT create a JFX application that compiles. On Fri, Sep 27, 2019 at 6:58 AM Geertjan Wielenga wrote: > The Gluon OpenJFX Maven sample archetypes have been part of Apache > NetBeans since 11.1. > > Gj > > On Fri,

Re: Hopefully close to the finish line with Java 11 & FX

You can also easily make a JavaFX project with NetBeans if you use a Gradle project - as everyone should ;-) https://openjfx.io/openjfx-docs/#gradle But you do have to manually add the javafx-plugin to your Gradle build script. Perhaps we can get

Re: Hopefully close to the finish line with Java 11 & FX

Scott, glad to hear I'm not the only one with major headaches. Java 8 and Java 11 are such vastly different creatures I don't see how anyone would expect NB to address both equally well. It militates for a break in compatibility with the IDE in my opinion. Those who want to stay on Java 8 can

Re: Hopefully close to the finish line with Java 11 & FX

The Gluon OpenJFX Maven sample archetypes have been part of Apache NetBeans since 11.1. Gj On Fri, Sep 27, 2019 at 2:54 PM Chuck Davis wrote: > Chris: > > NB has not made a JFX project that works since JDK8. The JavaFX > application should be taken off the new project menu until such time as

Re: Question on Netbeans 11 and C++

Would be great to see C/C++ support via Gradle’s 'cpp-library’ plugin. A smooth Java + JNI project setup would be welcome along with it. Existing NetBeans C/C++ support on Windows is not very practical. Bordering on almost unusable actually. (It requires use of a toolset that is virtually

Re: Hopefully close to the finish line with Java 11 & FX

Javafxpackager was removed along with several other things in Java 11. Sadly this was done with no reasonable path forward - there was no replacement for javapackager (it was renamed from javafxpackager because it isn’t strictly related to JavaFX), nor were many of the removed modules

Re: Hopefully close to the finish line with Java 11 & FX

Scott and All -- > The target should be 11 not 1.11. Thanks to Scott! I'm not sure where the 1.11 came from -- I think it was generated somewhere out of my control. (Yes, passing the buck.) In any case, one step forward has gotten me to another problem, which I believe is with

Re: Question on Netbeans 11 and C++

Donation in this context means Oracle donation of code to the ASF. (and not money) Maybe that provides more sense to GJ comment. ;) Am 27. September 2019 10:25:35 MESZ schrieb Geertjan Wielenga : >Yes, that is called the Apache Software Foundation. > >Gj > >On Fri, 27 Sep 2019 at 09:24, Ulf

Re: Question on Netbeans 11 and C++

Am 26.09.19 um 23:02 schrieb Peter Kovacs: > I do not understand the question. Can you elaborate? My understanding of "donation" was, that there is a kind of crowdfunding to support the C/C++ plugin. -Ulf - To unsubscribe,