Right. One thing to also note is that the CSS ref and FXML ref are part
of the API docs and are maintained. It's the tutorials that aren't.
-- Kevin
On 8/31/2018 2:41 PM, Tom Schindl wrote:
Well historically I think that some of those document fxml/css have been
released under BSD. I know that because I needed that to ship e(fx)clipse.
See
http://cr.openjdk.java.net/~kcr/RT-34389/javafx-samples-8.0.0-ea/src/Ensemble8/cssref/cssref.html
Tom
On 31.08.18 20:58, Kevin Rushforth wrote:
I can at least ask whether this would be possible.
-- Kevin
On 8/31/2018 11:51 AM, Mike Hearn wrote:
Well, I'm not thinking about my needs here - I've already learned the
framework. I'm more wondering how people will learn and get the tools
for JavaFX development in future. Up until Java 11 you could at least
go to a single website, click on fairly obvious links, end up at the
Java 8 docs for JavaFX and start learning. Post Java 11 .... where do
users go? A wiki page? That seems rather hard to find.
Given the Oracle has graciously open sourced so much of the Oracle JDK
for OpenJDK, I wonder if there's any chance of the docs being open
sourced too so they can be reformatted, refreshed and put onto a new
website by the community? It seems a shame to let them bit-rot.
On Fri, Aug 31, 2018 at 19:21:56, Kevin Rushforth
<kevin.rushfo...@oracle.com <mailto:kevin.rushfo...@oracle.com>> wrote:
Ah, OK. As far as I know, the FX 8 non-API docs aren't going
anywhere, but as you note they also aren't being updated.
They are not under an open-source license. You would need to read
the license to see what the terms of use are and whether that
would meet your needs.
-- Kevin
On 8/31/2018 9:36 AM, Mike Hearn wrote:
I was actually referring to all the docs that *aren't* JavaDocs,
like the tutorials, the CSS reference, the getting started
guides, interop guides etc.
As far as I know they haven't been updated since Java 8, however
the API is backwards compatible so they are still useful learning
materials. I am also not sure if they're open source licensed
though.
It would be a huge pity and a big drag on adoption if the
community had to effectively produce an all new set of non-API
docs _from scratch_.
