I’ve just pushed the initial support for attribute validations to the e(fx)clipse-repository. Here are the screenshots on how this looks like:
The foundation is there now all I need to implement are the validation rules for the various attributes. I’m going to publish the next release once this work is done which is more or less boring.
Please download the latest version from efxclipse.org
On Friday I’m going to be on holiday for about 2 weeks but I wanted to release 0.0.2 before so here it is. The new features are:
- Improvements for value property proposals
Further value property improvements will follow in the next release
This will make it easier to share your JavaFX-Projects with other users
This wizard creates a Java-Project and automatically adjusts the Java Build Path to hold the configured JavaFX SDK
- Automatic JavaDoc-Integration
You can download the p2-archive from my e(fx)clipse github-repo and install it into you Eclipse SDK using the Install Wizard.
In you have feature ideas, find bugs (highly likely in a 0.0.2 release) please report them here.
Just a short notice. Jaxenter.com has published a short interview with me about my tooling efforts for JavaFX for Eclipse I recently blogged about.
So there are many 3.x-RCP application and their developers who’d like to run their RCP-Apps ontop of the Eclipse 4.1 RCP (Attention: Don’t mix this up with the Eclipse 4 Application Platform – I’ve blogged about lately).
The Eclipse 4.1 RCP allows you to run your RCP applications unmodified ontop of the Eclipse 4 Application Platform – it is more or less the compat layer provided by Eclipse 4.1 (e.g. to make PDE and JDT run ontop of it).
The component diagram of such an application looks like this:
As the standard example I’ll use the RCP Mail Demo generated by PDE:
You should now see an application like this:
Obviously not what we’d expect because it should look something like this:
What you are seeing here is a known bug which is fixed in CVS and if you happen to download an I-Build >= I20110630-1005 you should not see the problem any more.
The important question for you is. Why you should at least try this? Here are some possible reasons:
- Get a more modern L&F by default like Thomas Kratz describes in his blog
- Provide feedback for things not working to the team so that we can probably even fix them in 4.1.1 so that you can ship your product in autum using Eclipse RCP 4.1.1
- Use the Workbench ModelTooling to better understand your RCP and interact live with it
I’d like to discuss the live model tooling a bit because I think it is a very interesting feature provided to Eclipse 4 applications. To some extends it replaces the Plugin-Spy used to in the 3.x world when you are interested where things are coming from, … but it provides much more.
The first thing you need to do get the tooling is to install it from the e4-Update-Site:
If you now add the following bundles to your launch config:
and hit the “Add Required Plug-ins” and launch the application you can launch the interactive tooling using ALT+SHIFT+F9 which opens an extra dialog like this:
The really interesting thing with the e4 live instance tooling is it not only a passive tool but allows you to interact with the running application instance:
- Using the UI (moving nodes in the tree on the left, enter new values into the form fields on the right)