I haven’t blog for a while because I had to prepare a special coming (not arrived yet).
You have probably heared that a JSR has been started to normalize JavaFX Application Framework: JSR 377 Desktop|Embedded Application API.
I have made a summary of which features are supported into JRebirth.
As you probably know JRebirth has a powerful thread engine that kick away all coding complexity that could lead to User Interface corruptions, lags or the worst one a totally frozen interface.
It’s really difficult to create dynamically a lot of threads without adding some bugs to the application. JRebirth provides a powerful way to simplify your developments.
With the advent of Java 8 (with Method References) and JRebirth 8, it’s now possible to chain and combine Tasks running into specific Thread in a very convenient way.
Last week I saw an interesting blog entry from Kynosarges that deal with the missing feature Platform.runAndWait(…) that was available into Swing.
While I was reading it, I figure that JRebirth Thread Engine already does the job !!!
As a remember JRebirth Application framework provides 4 kinds of threads:
- JAT ==> JavaFX Application Thread to perform all graphical updates
- JIT ==> JRebirth Internal Thread (perform JRebirth wave registration and other custom internal stuff)
- JTP ==> First Thread Pool (perform long task)
- HPTP ==> Second Thread Pool to perform higher priority task
Let’s see how to do run a UI task and wait before doing something else, we will play with some JRebirth Commands, the threading engine is totally hidden from developer sight.
Today I share a short video about JRebirth Workbench work progression. I have uploaded it on YouTube some days ago but I didn’t blog about it.
I’ve just seen the Tom’s blog entry that demonstrated a really nice tweaked TabPane build with Jonathan and perhaps available soon in OpenJDK (see the blog entry here for more information).
My widget is not as nice as their but the major part of my work is related to integration into JRebirth Component project.
In 2 words you can consider that JRebirth [Core+Component] will do the same job than e4 by using a different approach ( A Model from JRebirth is equivalent to an e4 part).
PS: Some people can ask themselves why (TF***) I’m reinventing the wheel instead of using e4 whereas I’m also an Eclipse developer. The answer is given by the framework’s name itself ! I’m really confident that we can do complex things in a simple way and mainly thread-oriented.
I’m upset to see my Eclipse (IDE and RCP) lagging all the day… (and even crashing, Java8+Luna+m2e+W8 doesn’t work anymore on my laptop… )