Cross IDE Dev-Support for “e4 on JavaFX” – We are almost there


In the last few days I made a major step towards supporting all major Java-IDEs (Eclipse, Netbeans, IntelliJ IDEA) to develop “e4 on JavaFX” applications.

The key to this multi-IDE support is that we don’t use the MANIFEST-First approach from PDE but we use:

  • Maven 3.5
  • bnd-maven-plugin
  • A custom maven-plugin for launching in Netbeans and IntelliJ

Eclipse

For every member on your team who likes the Eclipse IDE.

In Eclipse we use a custom launcher who uses the maven-project dependency information to launch OSGi and install all necessary bundles.

Netbeans

For every member on your team who likes Netbeans

As you notice hot-code replacement is not yet working (or maybe I’m using Netbeans wrong?) Is there anything i need to do after having changed the file to hot-swap it?

IntelliJ IDEA

For every member on your team who likes IntelliJ

As you notice hot-code replacement is not yet working (or maybe I’m using IntelliJ IDEA wrong?) Is there anything i need to do after having changed the file to hot-swap it?

This entry was posted in e(fx)clipse, Uncategorized. Bookmark the permalink.

10 Responses to Cross IDE Dev-Support for “e4 on JavaFX” – We are almost there

  1. Marcelo Ruiz says:

    Tom
    Wow! That looks Amazing! After that works, Gradle is around the corner!

    Regarding your question about NetBeans, here is what I found in Stack Overflow (https://stackoverflow.com/questions/10084289/how-to-use-hotswap-in-netbeans)

    1- Run your app in “debug” mode (something you’re doing)
    2- Modify your .java files and save them
    3- Click on the “Apply Code Changes” button that appears on the toolbar (it looks like three linked green rectangles, or Tools -> Options -> Java -> Java Debugger -> General -> Apply code changes after save)

    I hope that helps!

  2. Kevin says:

    Hi Thomas,

    I would like to ask questions about getting started with your e(fx)clipse examples.

    Is the code in this demo the same as the examples in the “e4 on JavaFX with the bnd-maven-plugin” (https://github.com/BestSolution-at/e4-efxclipse-maven-sample and https://github.com/BestSolution-at/maven-e4-launcher)?

    Can you describe which type of import to use for these projects into an eclipse workspace to run the demo (i.e. General, Maven or PlugIn development project)?

    • Tom Schindl says:

      Yes and no – it is that code but I have not yet pushed the changes because I first have to publish the maven-plugin. Stay tuned for updates on that next week

  3. Kevin says:

    Thanks for the reply Tom. Also, can you offer some guidance on importing the existing projects? I’ve not been successful with getting the code to run in my environment (Eclipse Oxygen), so I want to know if I’m missing some vital import step.

    Thanks again!

  4. Kevin says:

    Hi Tom,
    I read one of your other responses. I will move my question to the forum.
    Thanks!

  5. kerner1000 says:

    That’s awesome! Thank’s for cracking that nut!

  6. Pingback: JavaFX links of the week, August 28 | JavaFX News, Demos and Insight // FX Experience

  7. Daniel says:

    You know what would be great to port to other IDEs as well? FXGraph. Actually a colleague of mine has more or less switched over to IntelliJ. But he frequently returns to Eclipse only because of the FXGraph DSL & the live preview… 😀

    • Tom Schindl says:

      Right any volunteers to help with that? The first and most important thing we need to port is the e4-model editor because without that writing e4 on JavaFX applications is not really funny

  8. Maybe the cutest thing on Intellij would be if we could use a BndRun file to launch, as it has qutie nice an integration for that,

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.