Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] e(fx)clipse participating in Mars release

a) Does it Help
---------------
Yes it does help IMHO.

Take for example the GEF4 people they have never ever thought about how
JavaFX gets on the classpath they just use it like they use any other
thing that is part of the JDK, with the small difference that they
import javafx-packages in their MANIFEST.MF.

And there's more to JavaFX-SWT embedding than just getting FXCanvas on
the classpath? e.g. I guess most people embedding JavaFX into SWT with
the help of e(fx)clipse don't know that they need to call
Platform.setImplicitExit(false)

b) Can an EPP package use JavaFX
--------------------------------
Sure it can. I'm building an EPP like distro at
http://efxclipse.bestsolution.at/install.html using the p2-director to
install e(fx)clipse into a plain Eclipse SDK (+some WST, m2e, ...), p2
is clever enough to understand that there's an AdapterHook bundle is
about to be installed and corrects the config.ini.

c) On repackaging + Equinox classloader loading ext
---------------------------------------------------
It is a bad idea to rebundle anything from JDK because e.g. FXCanvas
calls out to *internal* JavaFX APIs so while your application will work
with JDK8u20 nobody on the world guarantees that it will still work with
JDK8u40 unless you use the the jar that resides in your JDK.

You can do that with Equinox-Specific MANIFEST-Entries but that still
leaves you with the heavy change of modifying the Equinox Classloader
Hierarchy - I hoped Tom Watson fixes that Equinox specific thing with
the Equinox rewrite but apparently it was not done.

Tom

On 21.08.14 16:11, Doug Schaefer wrote:
> I guess this raises another question. What about the other way. e(fx)clipse doesn't get in the way, but does it help either? i.e. With e(fx)clipse on the release train, would it be possible to have an Eclipse EPP package use JavaFX?
> 
> All the magic required to get this actually running really confirms what many people are telling me, that JavaFX is ready for prime time. I love the direction, but there are a lot of hurdles to actually use it in product. In our testing at QNX we did change the classloader hierarchy to include ext, and we bundle-ified the swt-javafx jar. Worked but not sure we can do that in the Eclipse context.
> 
> Thanks,
> Doug.
> ________________________________________
> From: cross-project-issues-dev-bounces@xxxxxxxxxxx [cross-project-issues-dev-bounces@xxxxxxxxxxx] on behalf of Tom Schindl [tom.schindl@xxxxxxxxxxxxxxx]
> Sent: Thursday, August 21, 2014 3:37 AM
> To: cross-project-issues-dev@xxxxxxxxxxx
> Subject: Re: [cross-project-issues-dev] e(fx)clipse participating in Mars release
> 
> We are still using OSGi-AdapterHooks but so do others on the release
> train as well but we are not modify any classpath nor do we modify the
> classloader strategy of Equinox so I can't see how we can affect others
> inside the IDE.
> 
> As far as I can tell there's no other option than Adapter-Hooks to get
> JavaFX embedded in the Eclipse IDE because the swt-javafx bridge is not
> on ANY classpath.
> 
> For JavaFX8 in OSGi without adapter-hooks you'd have to modify the
> Equinox-Classloader hierarchy to include the extension-classpath which
> most likely breaks many other things and would still not fix your
> swt-javafx embedding.
> 
> Other IDEs built on top of Eclipse (e.g. STS) have already adopted our
> AdapterHook and so do others like GEF4 and hopefully many others as well.
> 
> To sum up, I can't see how having e(fx)clipse on the release train (and
> maybe in a download package) can affect others using JavaFX beside
> takeing the burden to understand how much such an integration has to
> work in every detail.
> 
> Tom
> 
> On 21.08.14 09:23, Max Rydahl Andersen wrote:
>> On 20 Aug 2014, at 10:46, Tom Schindl wrote:
>>
>>> Hi,
>>>
>>> e(fx)clipse would like to join the Mars release as a +3 component
>>> because we depend on Xtext who is +2.
>>>
>>> Our current plan is to contribute e(fx)clipse 2.0 because this is the
>>> first time we are joining (I need to make myself familiar with the
>>> process) I'm not sure we manage to contribute to M1 in time.
>>
>> I'm curious - Did you find a way to use javafx without doing tweaks on
>> the classpath/eclipse.ini
>> that potentially affect others using javafx ?
>>
>> /max
>> http://about.me/maxandersen
>> _______________________________________________
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 



Back to the top