@Juan nice screenshots, is that Gluon Shine?

I upgraded the OSGi dependencies, so the OSGi Felix package on the web site is working again 🙂

@Juan Yeah, looks beautiful

@edvin, about the issue https://github.com/edvin/tornadofx/issues/667 Booleans do work correct? So they are handled with a different method?

Anyone get this error before?

Are you running Java 9?

Yeah. Downgrade time?

Yeah. The top of the TornadoFX readme says:

* Important: TornadoFX is not yet compatible with Java 9 *

Ahhh. I had read up on issues and they were from like a year ago saying that J9 support was coming soon 😋

That's what I get for not doing my homework

Its not easy to support Java 9 for JavaFX. Especially, if your library is using too many internal APIs

And even if you get around all those bugs, the benefit was negligible as Oracle just hasn't been giving much love to JavaFX. With the JDK 11 separation, this should hopefully change.

Yeah, looking at the github OpenJFX mirror, things seem to be going in the right direction 🙂

I seem to be getting the same issue running Java 8. A little more troubleshooting to do, though.

Mm. Yes, 100% Java 8 and I'm still running in to this issue?

Nevermind! So many things to change 😣

val path = configurable.configPath.apply { if (!Files.exists(parent)) Files.createDirectories(parent) } Why check? it doesn't throw an exception if the directory exists (due to the s after createDirectorie) Component[81]

@mikehearn Thank you!, It isn't, it's plain Javafx @edvin Thank you!

@Juan could you maybe publish a blog post or something about the CSS and approach you're using?

@edvin where are the java 9 incompatibilities coming from? using internal APIs?

that's a shame .... i'm trying to use j9+ for my new projects. i didn't have any difficulties yet and i used tornadofx on java 10

i guess i didn't use the features that don't work

ah, this i guess - https://github.com/edvin/tornadofx/issues/587

@mikehearn There are several issues, both with APIs that were public but are now private, renamed classes, functionality with no public API anymore, adapting to the module system etc. It has to be done though, so I will start looking at it soon. Will do one release after merging som PRs, then start looking at J10 compatibility.

hm, bummer. they have a github repository these days. i'm not sure what happens to PRs that are merged there, but I do see them getting merged and oracle employees comment on the github

perhaps now it's open the compatibility policies can be re-evaluated and more stuff can be made public. on the other hand, the relative stability of javafx (e.g. compared to the js ecosystem) is one of the nice things about it

so it's tempting to ask for everything to be made public, but then, that'd harm the stability

@mikehearn When JavaFX is removed from the JDK they would have to make everything open/public, wouldn't they?

@edvin The process has already started: * http://mail.openjdk.java.net/pipermail/openjfx-dev/2018-February/021335.html * http://mail.openjdk.java.net/pipermail/openjfx-dev/2018-February/021371.html * http://mail.openjdk.java.net/pipermail/openjfx-dev/2018-February/021456.html