well, that's just awesome now... now I just have to update it...

btw, I found a maybe issue with FXLauncher...

Yeah?

if you have a versioning that starts with a letter it won't build

found it because I was stupid and tagged my branch v1.0.1

completely broke the build and freaked out for an hour.

Where does FXLauncher care about your branch name?

because I auto pull version from tags

Where does the version affect FXLauncher? (brb)

oh, I don't know, but it breaks it!

in gradle I can put version 'v1.0.1-1-gfa70618'

and it will go through all the steps for a native installer except generate native

the only thing I haven't done correctly yet is automate s3 security

Btw, tornadofx is awesome... I'm a kind of person who re invents the wheel, and i had already written a less round and more bumpy version of controllers and api and json parsing

So much better!

Fxlauncher should not care about your version at all.

Working with Kotlin and jdbc is becoming somehow frustrating. The execution of a prepared statement is always returning false, even when the query was successful and the data was added to the db. Hard to give a correct feedback to the user.

pst.execute()

Always false?

did you look at kdbc?

its one of @edvin's projects and makes a DSL around jdbc

@ron, @edvin told me that kdbc was not ready yet.

you could of course use JPA

The last time I worked with JPA, I used eclipseLink implementation which was really nice. I will give it a try. But as the JPA requires pojos for annotations am I going to redesign my models because my models are built with the JavaFX /TornadoFx properties.

KDBC is actually ready enough, and there are no known bugs, but it might be a little early.

Gosh, I'm so lazy some times:

@User uploaded a file: Untitled

I use it in Views, like this:

@User uploaded a file: Untitled

grins I just did something like that in C++ #define NR isNotReady(*db)

I should start reading all that has changed in tornadoFX

how much has changed?