@carlw Thank you!!!

@Ruckus You could place it in

Nodes.kt

perhaps? It's easy to move without ramifications if a better place shows up later!

Sounds good to me

@Ruckus I tried to conviert this int typesafe css but I failed, since you know best about the css, could you give it a shout?

@nimakro There's actually an open issue to support

ladder

and

derive

functions (https://github.com/edvin/tornadofx/issues/220), but I never got around to finishing it. I'm still not sure what a good solution for its problems would be. In the meantime, you can just use an unsafe/raw call and give it the string. Sadly that's the best I have for you.

Something like

unsafe("-fx-shadow-highlight-color", raw("""
    ladder(
        -fx-background,
        transparent 0%,
        derive(-fx-background,40%)   5%,
        derive(-fx-background,60%)  70%,
        derive(-fx-background,100%) 85%,
        derive(-fx-background,100%) 97%,
        derive(-fx-background,-10%) 97.5%
    )
""".trim().replace(Regex("\\s+"), " ")))

Hey everyone. I am having problems parsing multi-level json objects using the TornadoFx json parser. Here's my json response.(it's a rest api endpoint for flights resources ). When trying to get the string values from the arrival object, it's not updating to ui .

@eddy_wm Can you post your domain object that parses this json payload?

override fun updateModel(json: JsonObject) { with(json) { flightNumber = string("flightNumber") status = string("status") with(string("arrival")){ arrivalCity = string("city") } } } That's my update function, the two first properties are getting rendered just fine. The problem comes when I am trying to get values from the inner json object "arrival", I have tried some tricks, but with no success.

@eddy_wm You're extracting a String, but you should extract a JsonObject for it. Even better, if you have an

Arrival

object that also supports JSON, this can be automatically loaded with

arrival = jsonModel("arrival")

.

@eddy_wm Can you post the JSON as text?

Never mind, I wrote it myself 🙂

@User uploaded a file: How to parse JSON like a boss :sunglasses:

@eddy_wm Look at the code above, that's a complete example with all the domain objects and even a unit test 🙂

Using the

jsonModel

function makes your code incredibly clean and nice. In fact, this is all you need in

Flight

to parse that JSON blob:

@User uploaded a file: Untitled

I created a common superclass

TimeInfo

for

Arrival

and

Departure

, since they contain the same fields. Notice how the timestamp is turned into a

LocalDateTime

object by getting the string and parsing it using a formatter defined in the companion object.

😳 wow. That was super fast @edvin . I was offline for a moment.

Is there a function/property in the Rest class that can help me to be sure whether I am sending the correct request by printing the final request URL when query strings have been applied to the base URI. Because in the rest api I designed I have end-points like this one "http://127.0.0.1:8000/api/v1/flights?include=arrival,departure" with query strings. That can be very useful when debugging the program.

@eddy_wm I don't think there is anything that helps you with constructing the URL, so you would have to build and validate the URL yourself.

@edvin would the apache http client work with loggin?

-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog -Dorg.apache.commons.logging.simplelog.showdatetime=true -Dorg.apache.commons.logging.simplelog.log.org.apache.http=DEBUG -Dorg.apache.commons.logging.simplelog.log.org.apache.http.wire=ERROR

?

set the special "use" flag you came up with

For instance if I am trying to access an endpoint like this one "http://127.0.0.1:8000/api/v1/flights?include=arrival,departure" I may build it through these steps

api.baseURI = "<http://127.0.0.1:8000/api/v1/>"  val	params	=	mapOf("include"	to	"departure,arrival")

and finally

api.get("flights${params.queryString}")

. At the end I may not be quite sure whether I built the correct URL, that was my concern. Nevertheless, I am very thankful @edvin.

the "wire" -D logger setting is the key....setting it to DEBUG lets you capture what gets sent over

@eddy_wm sorry for not including code, but can you call this and pass along the options from my previous message (modify the ERROR to be "DEBUG") Rest.useApacheHttpClient

@eddy_wm You could check the resulting string, but you might as well just inspect what you have in your params map 🙂

@carlw That should work 🙂 I never use it myself, since the default engine fits all my needs (or I make it fit.. hehe :)

@carlw, I have tried that but I am not getting useful information, I might be missing something...