Refactoring JavaFX Builds & Sources

[Richard Bair]

> Tangent alert: all the rest of the code.
> 
> So now that 7u13 is out what are teh remaining gating factors on getting the rest of the OpenJFX stuff out?  I am sure the Developer Preview of JDK8 will be consuming alot of bandwidth, but are there any other aspects we should be aware of?

The rest of the code falls into 1 of 3 categories:

1) Code that was waiting for 7u13. This code is now cleared to go out and we should see it come out in the next couple weeks. Artem just about has javafx-embed-swing and javafx-embed-swt ready to go. I think the following will also be ready to go late next week  / early week after (but need to double check):

	decora-d3d
	decora-jsw
	decora-prism
	decora-prism-ps
	decora-prism-sw
	decora-runtime
	decora-sse
	glass
	javafx-beans
	javafx-iio
	prism-j2d
	prism-ps
	prism-util

2) Code that is still going through the meat grinder. With the security work ongoing, our schedule is being impacted -- some of these may well be able to come sooner and some a little later:

	javafx-ui-quantum
	javafx-ui-webnode
	prism-common
	prism-d3d
	prism-sw
	webkit
	webnode-prism
	prism-es2
	prism-es2-eglf
	prism-es2-eglx11
	prism-es2-mac
	prism-es2-win
	prism-es2-x11
	javafx-ui-desktop
	media

3) Code that won't be opened or needs an open equivalent to be written.
	javafx-deploy
	javafx-font

javafx-deploy has applet deployment specific code (the non-applet stuff such as the app co-bundling / javafxpackager code is out / going out).

javafx-font has the proprietary T2K dependencies. This dependency needs to be replaced so we can then have a fully open build. I want Felipe to prototype an implementation that delegates directly to the native font code for measurement / glyph generation / layout / etc, rather than using Freetype on all platforms. We need to then get performance #'s on this. I want Felipe to work on this in the open source from the start. The only issue here is that Felipe is also fundamentally involved in bug fixing and our backlog is growing quite large.

That's what I know today. I've emailed the team to find out specifics about those items in #2 above to see if any of them (such as quantum / web node) can get moved into category #1 (or at least make it out by the end of February).

Some of the embedded related code is tied up in legal approvals and will hopefully be resolved soon. But with legal -- you know how that goes (so prism-es2-eglf, prism-es2-eglx11). However getting the embedded code open is a high priority item so I'm optimistic on it.

Thanks for the patience, we're going as fast as we can.

Richard