There's an old plugin for this I used back in the day:
https://github.com/rterp/JavaFxPropertyHelperNBPlugin
On Thu, Jun 6, 2024 at 1:53 PM Will Hartung wrote:
>
> JavaFX properties look like this:
>
> StringPrroperty nameProperty = new SimpleStringProperty();
>
> public String getName() {
>
.
Thanks again and all best!
Steven
On Mon, Oct 11, 2021 at 8:57 AM Neil C Smith wrote:
>
> Hi Steven,
>
> On Sat, 9 Oct 2021 at 16:48, Steven Yi wrote:
> > 3. Does anyone have recommendations here? I think I might go down the
> > same route as PraxisLive and start bundling
Hi All,
I hadn't been testing my RCP app on Windows for a while and a user
reported that they installed my program and got a message of "Cannot
find Java 1.8 or higher" after double-clicking the .exe. I checked and
found that to be the case with both my application as well as a basic
Maven
Congratulations on the release! Is there any timeframe for when RELEASE124
libs will be uploaded to Maven for RCP app devs to use?
Thanks!
Steven
On Sat, May 29, 2021 at 5:32 AM Geertjan Wielenga
wrote:
> Hi all,
>
> The Apache NetBeans team is pleased to announce that Apache NetBeans 12.4
>
Hi All,
I was working on a BeanTreeView in a platform app and found a strange
oddity that I'm not sure if I'm dealing with it the right way. If I
implement clipboardCut() in a way similarly to that found in:
I find the distinction between LTS and feature release is great, but I
do find the use of the minor number to denote a feature release a
little confusing. I think it's just a little cognitive dissonance
between semantic versioning practice, pre-Apache Netbeans release
cycles, and current Netbeans
I forgot to mention that I think I identified the cause of this and
filed issue NETBEANS-3332:
https://issues.apache.org/jira/browse/NETBEANS-3332
On Thu, Oct 31, 2019 at 1:43 PM Steven Yi wrote:
>
> Hi All,
>
> I ran into this today when I switched to JDK 11:
>
> [INFO]
pplication and class patching now works. This also changes the
module name but it's fine in my case as these modules are not used
outside of this application.
Thanks,
Steven
On Sun, Nov 10, 2019 at 4:50 AM Steven Yi wrote:
>
> Hi Thomas,
>
> Thanks for the reply. I had tried that bef
an change in my
project to get this to work, or if this is a legitimate bug in
Netbeans. (Or if this is something that would work for
run-of-the-mill maven projects but doesn't for Platform apps.).
Any suggestions appreciated!
Thanks,
Steven
On Sun, Nov 10, 2019 at 3:38 AM Thomas Kellerer w
Hi All,
Having moved to Maven with my platform app, I've got a question about
workflow. Right now when I'm working on a change in one of my modules,
to test it, I have to:
1. Build the current module
2. Select the main application module
3. Run the main application module
In the past, when
Hi All,
I ran into this today when I switched to JDK 11:
[INFO] Compiling 6 source files to
C:\projects\blue\application\target\installerbuild\nbi_all\ext\infra\build\engine\build\ext\engine\build\classes
error: Source option 5 is no longer supported. Use 6 or later.
error: Target option 1.5 is
kflow on migration or tips in a web or confluence page.
>
>
>
> Best Regards
>
> Eric
>
>
>
>
>
> *De :* Steven Yi
> *Envoyé :* jeudi 31 octobre 2019 04:36
> *À :* users@netbeans.apache.org
> *Objet :* Re: Platform App, JavaFX, and Java 11
>
Steven Yi wrote:
> Hi All,
>
> I've been working on migrating my platform application Blue to Maven. I
> have this working with RELEASE111 and Java 8. However, when I move to Java
> 11, my app starts up, show the splash screen, shows messages about loading
> modules, then disa
Hi All,
I've been working on migrating my platform application Blue to Maven. I
have this working with RELEASE111 and Java 8. However, when I move to Java
11, my app starts up, show the splash screen, shows messages about loading
modules, then disappears and nothing happens. My application
14 matches
Mail list logo
