if I do that I am wondering where to leave buttons like "save, undo, reset"

isn't that what the buttons on the top bar are for?

they are not hooked up yet, the "save" button there will save the file not an entry

the reset will reload the file

is it possible to save an entry without ever saving the file?

yes

if you save/change an entry, the file will be marked dirty and when you exit the program the program reminds you that you have unsaved changes

which you can ignore if you want

then the changes you have made are gone

I see - so you want to commit or rollback edits to the viewmodel for the selected entry...

yes

How about a button bar below the accordian in the details drawer?

ja that is my thought at the moment

@User uploaded a file:

It's also possible to make the buttons in the top bar change to save whatever is focused if you will. But in this case I think the buttons are too far from the data, and it might feel strange. You could maybe use a context menu?

Sorry for being so distant this weekend, I've been working on KDBC for the most part 🙂 Back to writing documentation on Monday 🙂

@edvin is KDBC similar to jOOQ?

or close to it? in functionality/design...

@jchildress It might have some similarities, but there is no code generation in KDBC. It's probably more explicit, requiring you to wire the result of the queries to your domain objects manually. I believe this is a good thing, at least with Kotlin, where there is minimal boiler plate. Also the joins and column selections are completely explicit, so you have 100% control of what's hitting your database and how your domain objects are created.

I've added some examples and information to the README: https://github.com/edvin/kdbc

It might look weird at first, but the approach with

class per query

really works great for sql code/join reuse.

k, thank you

I'll try to create a screencast for it, maybe tomorrow 🙂

Interesting challenge on SO today 🙂 Never tried to unsubscribe to events before: http://stackoverflow.com/questions/42465786/how-to-unsubscribe-events-in-tornadofx/

@edvin If it isn't already in the book, add it 🙂

@permalmberg Thank you! I needed that push 🙂 Will do!

@permalmberg Hmm.. I should be able to create a

subscribeOnce

function. That would be pretty handy.

@edvin Yeah, that can then be used to do N-subscriptions by the user

@permalmberg We could even support

subscribe(times = 4) { listeningCodeHere() }

but if you can do subscribe-once, can't you also do a working unsubscribe() ?