Possibly. But even if the source code becomes public, the APIs may not be.
Also, don't underestimate the "impedance mismatch" between the FX and Java2D rendering models. There is not a nice 1:1 mapping between the immediate mode style of Java2D and other similar APIs and the retained/multiple thread model used by JavaFX. On Feb 28, 2013, at 12:46 PM, Andrei Pozolotin <[email protected]> wrote: > there seems to be a promise here that all of prism will be public, or am I > misreading this > http://fxexperience.com/2013/02/february-open-source-update/ > > -------- Original Message -------- > Subject: Re: pivot + webkit? > From: Greg Brown <[email protected]> > To: Andrei Pozolotin <[email protected]> > Cc: [email protected] > Date: Thu 28 Feb 2013 10:28:20 AM CST >> JWebPane might be helpful if it existed, but unfortunately that work was >> turned into the JavaFX WebView which relies on Prism (private JavaFX API). >> >> On Feb 28, 2013, at 11:23 AM, Andrei Pozolotin >> <[email protected]> >> wrote: >> >> >>> webkit for java2d: >>> >>> http://fxexperience.com/2012/04/interview-with-peter-zhelezniakov/ >>> https://blogs.oracle.com/geertjan/entry/waiting_for_jwebpane >>> >>> >>> -------- Original Message -------- >>> Subject: Re: pivot + webkit? >>> From: Greg Brown >>> <[email protected]> >>> >>> To: Andrei Pozolotin >>> <[email protected]> >>> >>> Cc: >>> [email protected] >>> >>> Date: Thu 28 Feb 2013 09:26:47 AM CST >>> >>>>> I am curious if we go "level down" (almost JNI) >>>>> and try to talk to the underlying webkit wrapper for javafx, >>>>> would it be easier to integrate in pivot? >>>>> >>>>> >>>> I don't think so. The JavaFX port of WebKit is enormous and complex - not >>>> an easy thing to work with. Also, I think many of those APIs are hidden. >>>> >>>> You might be better off porting WebKit to Java2D yourself (maybe someone >>>> else has tried this?). >>>> >>>> >>>> >>>> >> >
