So you need to use it like

<http://api.post|api.post>("some/path${params.queryString}")

- which isn't ideal.

@edvin what was the json library that you use in tornadoFX?

@ron It's the reference implementation of

javax.json

, then I added some sugar on top of it.

Namely the

JsonBuilder

and lots of extension functions.

yeah just found, I am writing a java program that configures nexus using the rest api

and wanted a simple and fast json thingy

@ron This is a nice article about json libs for java http://blog.takipi.com/the-ultimate-json-library-json-simple-vs-gson-vs-jackson-vs-json/

ROFL I actually read that this morning 🙂

👍 😉

@ron Vertx has some nice json handling stuff in it as well as a nice HTTP client. http://vertx.io/docs/vertx-core/java/#_json http://vertx.io/docs/vertx-core/java/#_creating_an_http_client http://vertx.io/docs/vertx-web-client/java/

I've run into some issues where the Java runtime can't seem to differentiate between Long? and Int?, so I'm looking at changing the

json.add(string, int?)

and friends to

json.add(string, number?)

and dealing with the type inside that function istead.

Now this seems to have "spread" to the property handling as well. Have no idea what caused this, if I made an inadvertent change, or if something changed between jvm versions.

Using

workspace

it should be safe for a view to remove itself from the navigation stack like this...

override fun onUndock() {
		workspace.viewStack.remove(this)
	}

correct?

But after that undocking occurs, the forward nav button is still enabled, and when you click it you get an

java.lang.IndexOutOfBoundsException

@edvin it should be able to

what jvm signature does the method compile to?

@mikehearn Let me try to set up a simple test case and check.

This property ends up with a

Long

inside it:

var qty by property<Int>()

- but if I change the definition to

var qty: Int by property<Int>()

it's OK.

Weird.

Even weirder, this, in the same class, never fails:

var id by property<Int>()

Also tried changing to the new property syntax, same thing there.

I was on a wild goose chase. This has to do with a bug in

column.makeEditable

.

@kastork I updated your issue with a question 🙂

It works in my tests, so you probably define the boolean property different from my test. Kotlin is very picky about generics and native types.

@edvin I sent a PR with a test case

@edvin also, I noticed the maven build does not run

JsonTests

Kotlin and generics is completely baffling at times. It's actually much easier in vanilla Java.

@edvin heh, you should look at ceylon

Gavin King. He seems brilliant, but I've never seen anything he made that wasn't overly complex and hard to understand.

And even worse: It seems easy to understand at first glance.