I know it looks completely crashed but well this is what you get when running Kepler on BestSolution.at SWT port which delegates to JavaFX.
So there’s still a long long long way to go but to me this screenshot marks a huge break through. I could certainly need some help. So we opensourced or current port at https://bitbucket.org/tschindl/e_on_f.
Our current plan is to integrate it in the next few weeks into the e(fx)clipse project – where it originated from before we moved the code to Eclipse.org.
Hi Tom,
this looks really, really great and I would like to help you. Is there a plan from where I can pick a part to fix? I’m ust asking because I don’t want to start working on a thing and somebody else starts on the same thing too.
Regards
René
Hi – I suggest we use https://groups.google.com/forum/?fromgroups=#!forum/swt-javafx to coordinate until we have moved our codebase to Eclipse.org
Thank you so much, Tom. I started learning JavaFX on NetBeans but went to e(fx)clipse as my brain couldn’t handle NetBeans IDE behaviour. I want your effort to be successful so that I don’t have to learn all about JavFX.
Pingback: Java desktop links of the week, January 20 « Jonathan Giles
Pingback: JavaFX links of the week, January 20 // JavaFX News, Demos and Insight // FX Experience
Pingback: SWT on JavaFX is now at part of e(fx)clipse | Tomsondev Blog