No, not much.

Some of the reflection tricks can be thrown out anyways because we get some more public API functions in JavaFX 9.

hmmz looks like that jdk fixes some things that would be good in general for linux

Others we'll just have to work around.

That might be.

OK, good night guys 🙂

I hope they push the changes back to openjdk

night

night edvin

after a 13 hour day I need to relax:

the voice of that woman is incredible

@jchildress And thanks for spotting that bug :))

@edvin No problem. I hope to watch your new screencast tonight or tomorrow morning... Work has been very busy lately 🙂

@jchildress how are the slides coming along?

@carlw behind...

about to go get in traffic... got to love Houston...

Why didn't we add

fun Button.action(op: ActionEvent.() -> Unit) = setOnAction(op)

sooner? 🙂

We can add for example

async = true

as parameter as well to make it wrap the call in

runAsync

or something coroutines based down the line.

Sounds good to me, and thanks for your video I will watch it first thing in the morning 😀

@nimakro Thanks 🙂

@edvin So much for bed

I got this idea about action - just had to implement.

Added to

ButtonBase

,

TextField

and

MenuItem

.

@edvin Just watched the video, good job 🎉. I noticed that you are able to edit the TodoItems even though they are marked as inactive. I am not sure if there is an easy fix for that will check tonight, but you are probably faster anyways 😀 I really like your TodoItemFragment implementation, so do I understand that right that you basically implemented the TextFieldListCell class which comes with Javafx (204 lines of code) in only 40 lines of code in addition with extra functionality like a checkbox and a delete button...very cool At the end of your video you mention the event-bus, is there any benefit for a small app, like the todomvc is right now, to use events, then coupling the views to the controller directly like you did, or let's ask differently, when do you usually start using events over coupling the views directly? Thanks again for the good work!!

@nimakro It's easy to disable editing when the item is completed, but I didn't know that it was a requirement in the todo app. Are you sure it is? About the event bus, it's actually mostly a matter of preference. Many people prefer explicit coupling to events, others hate it. I really have never run into an app that is "too large" to benefit from injecting controllers or anything like that. Some use cases are better handled by event, but in honesty I don't think any functionality in the todo app would really benefit from it.

@edvin I don't know if it is a requirement from the todomvc project, I just felt wrong to me to be able to edit the text of a task that is marked as done 😉, but that's just me, so I guess we leave it for now. Thanks for clarifying the event-bus question, that's exactly what I was thinking 👍

Sweet 🙂 This got me thinking, and I think the

ListCellFragment

should get even tighter control over cell events. Will look at it tonight.

I sometimes use a combination of the both of them. in my 'style' an event to get a list? I dont like. Basically you would need 2 event to supprt that, one to signal "I want the list" and one that says "here is the list" I actually thought about this a lot because keepassFX has two threads running. There is the use case (we worked on that yesterday) where the server thread needs to ask something from the FX thread and needs to wait for the answer from the FX thread. this could be solved actually with coroutines (ask.await()) but there is (to my knowledge) no "send an event and wait for an answer"

events are inherently asynchronous in my mind

keepassFX currently has 2 events "fileOpened" and "entriesUpdated" this could probably be solved without events but for me this was the cleanest solution (mainly because most of the backing store is not FX enabled but are pojo's)