Re: Is the NetBeans Platform the best choice for a JavaFX only desktop application?

geertjan wielenga <[email protected]>
Newsgroups gmane.comp.java.netbeans.modules.openide.devel
Organization Oracle Corporation
Message-ID <[email protected]>
It's not something that's going to be done on the NetBeans side. The 
hybrid approach makes sense -- and the feeling on the NetBeans side of 
things is that the amount of effort in rewriting things like the window 
system to JavaFX isn't the best way for time to be spent, given how many 
other features there are to work on. There's a lot of work you'd need to 
do, though Sven Reimers (and the https://java.net/projects/efx project 
you referred to) is currently the closest to what you're looking for. I 
suggest working on that project, rather than anything else you might try 
to do.

Gj

On 27-6-2016 17:18, Marcelo Ruiz wrote:
> Hi Geertjan,
>
> Thanks for the information. I am looking for a no-Swing solution for this project. I do have the book JavaFX Client Programming for the NetBeans Platform, but they explore a hybrid approach, just like the tutotial for porting JavaFx applications.
> I sent a message to Hermien Pellissier because I was interested in the example she posted (replacing the Windows Manager). That is a starting point.
> Would it be possible to get some guidelines from the NetBeans Engineers into replacing swing with JavaFX counterparts? I know it won't be easy but I was wondering if they can point out which parts of the existing code will be good candidates for reuse. For example: Is the logic that positions TopComponents into modes easily reusable? What are the modules that will need to be replaced?
> I know from some bug reports that the engineers were encouraged to take a look at the possibility of porting the platform to JavaFX. Do you have any information you can share regarding the complexities they detected?
> Thanks!
>
> Marcelo
>
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.