and then you always get people who think you’re an idiot

I can imagine. When you add a feature to JavaFX it has to work for close to every one. That's a lot of responsibility, and a lot of things to consider.

Haha I totally get that especially as I try to think more globally. The day an API is adopted by thousands of devs and makes everybody happy... probably not going to happen anytime soon.

nope 🙂

I guess JavaFX is a bit verbose, but that's why it is so powerful. To cater for everyone you have to add a little verbosity. That's actually part of the "success" of TornadoFX - in many cases we just add sugar on top of all the existing power.

I suppose we can't do anything regarding type-safe CSS?

I gotta get to bed guys. Thomas: We can try to compile a list in the coming days and pass on to Jonathan?

Okay, I'll hold off : )

later

That is extremely hard to get right or at least enjoyable with the current Java 8 syntax. I played with reimplementing what we have in Java 8. It didn't feel anywhere near as elegant.

Yeah, and like @jonathan said the FP aspect needs to be somewhat checked.

I am the owner of JavaFX controls, CSS, and FXML, we can discuss topics in any of those areas

@jonathan we're going to have a lot of fun then! I'm sure you'll be sick of us by the time we finish executing the new specs

You can actually use just the type safe CSS from TornadoFX in a plain JavaFX project. It works perfectly 🙂

it just needs to be reigned in - need to pick the most important tasks and do them one by one

We'll sift through it. I'll go through my notes, GitHub issues, and GitHub pull requests to see what might fit in the openjfx API over the next few days

One feature that would be nice in the CSS front would be the ability to add a stylesheet as a string instead of a URL. I don't know if project jigsaw is going to cause any problems with the package hacked URL handler @edvin built for the CSS rendering.

so the css as a string?

instead of an external url?

Yeah. Currently we have a custom URL stream handler living under the

sun.net.www.protocol.css

package, instead of in the

tornadofx

package with everything else.

You could just use the CssParser to return a Stylesheet instance perhaps?

We support two things. A CSS url can either reference a class, and class represents a stylesheet so that it is rendered and delivered to the input stream of the URL hander. We also support stylesheets embedded in the url via base64 encoding.

Thanks @edvin 😀

You know how this works better than I

(Now I'm really off to bed. Later guys!)

Sleep well

@jonathan: I'm not sure if this would be a priority at all. I just work a lot with the type safe CSS in TornadoFX.

probably not

By the way, here is the stream handler I was talking about if you're interested: https://github.com/edvin/tornadofx/blob/master/src/main/java/sun/net/www/protocol/css/Handler.kt

@jonathan: By the way, what time zone are you based in (if you don't mind me asking)?