How to build openjfx in its current state

[Richard Bair]

Hi Mario,

>> Now that a *lot* of stuff is in the open, I'm trying to build without
>> linking to jfxrt.jar. I should get pretty far on that. Once the build
>> is succeeding up to the point it should, then I'll test against a
>> stripped down jfxrt.jar (that only contains the closed bits) so that I
>> can make sure the open build is working correctly.
> 
> I tried to put the openjfxrt.jar into my OpenJDK (and using it instead
> of the closed jfxrt.jar).
> 
> I don't get very far, because of some missing classes in the .beans
> package that are needed right away.

Even though I'm replacing the ant scripts with the gradle scripts, I'm first getting the open ant scripts to work right in part to help me get 100% up to speed on our build process and also so you guys don't have to wait a few weeks while I'm trying to get the new gradle scripts working. I should have it sorted today (famous last words).

> Do you have a list of the things that still need to be open sourced
> (even as an estimate if you can't disclose the list yet)?

These are now open source (yay!):
	javafx-embed-swing
	javafx-embed-swt
	decora-d3d
	decora-jsw
	decora-prism
	decora-prism-ps
	decora-prism-sw
	decora-runtime
	decora-sse
	javafx-beans

These should be out in less than two weeks:
	glass
	javafx-iio
	prism-j2d
	prism-ps
	prism-util
	prism-common
	prism-sw

These we're chasing down the final bits. I would say within a month if all goes well, a couple months if it doesn't.
	javafx-ui-quantum
	javafx-ui-webnode
	webkit
	webnode-prism
	javafx-ui-desktop
	media
	prism-d3d
	prism-es2
	prism-es2-eglf
	prism-es2-eglx11
	prism-es2-mac
	prism-es2-win
	prism-es2-x11

At this point we are ALMOST fully open source. The only remaining nugget (AFAIK!) is javafx-font. This presently relies on T2K. I don't want to plug in FreeType the way we did on the JDK side. Rather, I'd like the open implementation to be a simple thin-wrapper on top of the native APIs, so that we use Pango / Direct2D / Cocoa or whatnot in order to both give us the glyphs to draw and also to do line measurement / complex text layout / etc (right now we rely on a combination of T2K and ICU). The reason we think this will work for us is that with Java 8 we no longer officially support Windows XP, so we can finally leave GDI as our least-common-denominator out. (GDI just couldn't do what we needed, so we had to have our own implementation anyway, so it made sense to just use it across the board).

Richard