Comments for Tomsondev Blog

Comment on e(fx)clipse 0.0.12 released by Tom Schindl

Tom Schindl — Thu, 02 Feb 2012 12:55:48 +0000

Thanks for the compliment – as far as I know Netbeans 7.1 also got JavaFX 2.0 support. I think the main advantage in Eclipse is that I have Xtext which makes writing things like the CSS-Editor a quite simple task whereas in Netbeans they first had to add CSS3-Support to the CSS-Editor itself beside that e(fx)clipse has the advantage that it is not part of a big product with long release cycles.

One thing I know for example the Netbeans integration is a lot better is when it comes to example applications. I’ll have to take a look if I can add them as well to e(fx)clipse but that heavily depends on the license.

Comment on e(fx)clipse 0.0.12 released by Farrukh

Farrukh — Thu, 02 Feb 2012 12:30:37 +0000

Excellent Work shame for Netbeans team they are doing nothing in their IDE for JavaFX. this man single handedly doing super stuff keep going

Comment on e(fx)clipse 0.0.12 released by Tom Schindl

Tom Schindl — Thu, 02 Feb 2012 09:40:39 +0000

As far as I know there are no live streams – at this years EclipseCon Europe though most talks have been recorded and provided later on. In case you need support (on professional base or none professional) just let me know. If you are building products on top of Eclipse frameworks I can only suggest that you get to EclipseCon US/Europe to see what’s going on and chat with the developers directly.

Comment on e(fx)clipse 0.0.12 released by Juan Felipe Caro

Juan Felipe Caro — Thu, 02 Feb 2012 09:34:16 +0000

Thanks a lot Tom, we a re following your work with attention and we are seriously considering using it for our next generation products.

Is it possible to see your EclipseCon Conference via Web?

Comment on e(fx)clipse 0.0.12 released by Sébastien Bordes (@SebastienBordes)

Sébastien Bordes (@SebastienBordes) — Tue, 31 Jan 2012 20:08:25 +0000

Excellent work, thank you

Comment on SVG for FXML-Conversion by e(fx)clipse 0.0.12 released | Tomsondev Blog

e(fx)clipse 0.0.12 released | Tomsondev Blog — Tue, 31 Jan 2012 19:37:25 +0000

[...] started working on SVG and FXG to FXML-Converters as I already outline in one my last posts my plan was to add them to e(fx)clipse to allow you converting those external formats to JavaFX 2.0 [...]

Comment on e(fx)clipse 0.0.11 released by Tom Schindl

Tom Schindl — Tue, 31 Jan 2012 08:51:27 +0000

I have looked into this and the problem is that 1.8.4 is not cross-platform. I could now package the 1.8.x for win32 and 1.6.x for all other operating systems but I decided to stay away from this until subclipse provides cross-platform support through svnkit. According to their site support for newer SVN-Versions is coming in Feb so I decided to wait for 0.0.13 or 0.0.14.

Comment on e(fx)clipse 0.0.6 released by Tom Schindl

Tom Schindl — Tue, 24 Jan 2012 14:30:31 +0000

I never tried to run it on 3.6.0. I can give it a spin to see if I can make it run on 3.6 (I don’t think I’m using anything specific to 3.7 but I never tried) which means I have to relax the constraints else p2 will refuse to install it.

Is there a deeper reason you’ll have to use 3.6 (are there other plugins you’ll use who don’t run on 3.7) even if I can make it run on 3.6 it’s not a going be a reference platform and so not tested before releasing.

Comment on e(fx)clipse 0.0.6 released by Alan Frye

Alan Frye — Tue, 24 Jan 2012 14:25:29 +0000

I am in the process of getting started using JavaFX for some upcoming projects. I am currently using Eclipse 3.6. Will I need to switch Eclipse 3.7 in order to use this plugin.

Thansk

Comment on e4 – Fundamental Overview on the Eclipse 4 Application Platform by Tom Schindl

Tom Schindl — Tue, 24 Jan 2012 14:18:02 +0000

There are some problems when running RAP on the Eclipse 4 Application Platform. The most prominent is that one needs to replace the default IEventBroker through a RAP specific one because the default one uses the OSGi-EventAdmin which is a framework singleton and hence all RAP-Instances would communicate through the same channel.