I did a training of tornadofx at work today with several colleagues. It went really well!

@thomasnield So cool 🙂 I'm proud of what we have built and that it is actually used in companies to solve real problems 🙂

@thomasnield I committed the first part of the DataGrid docs to the guide today, will finish it tomorrow

I got hung up on researching OSGi again, so it goes slow 🙂 I'm currently looking at Apache Karaf. Really impressive stuff

@edvin If you want to feel even more validated, my colleagues and I don't work in IT. But a lot of IT folks are joining our team because we're rolling out really cool stuff. TornadoFX and Rx is allowing us to outpace the conventional software shops.

Cool I'll keep working on it on my end as well. I'm eager to read about that

So cool to hear 🙂 Right now it seems we have no new huge features to create either, so hopefully we'll have time to finish the guide as well. The only development I'm currently doing is the plugin. I want to support the alternate property style as @Ruckus requested and the sampler thing. That could be really good for adoption.

Awesome. I think it's a really good idea.

Great! I will have some time this weekend so I hope to have something to show you before Monday.

No rush I've been doing my best to balance a million things going on too

Yeah, we've all been a bit busy lately, but that's fine.. we're in a good place with no big issues pending

Welcome Fausto 🙂

@thomasnield Nice work on the YouTrack Issue. Would be fantastic if you got that into the stdlib!

@thomasnield kotlin is a very efficient language, tornadofx takes that adds a totally focused framework on top of that, no extra baggage, single responsibility to the max

@edvin I just read the guide about the datagrid maybe that chapter is becoming too big? Especially when people just want to read about listview or datagrid, it is not clear its there. Maybe split it up.

The datagrid section is completely focused on images maybe add a small example where a more complex (like a Fragment for example) is added?

oh and concerning big new features? a treeview or treetableview that is datadriven like the datagrid and listview?

@ron Thanks for the input, I will definitely add a more complex ui example to the datagrid part. I think @thomasnield is best qualified when it comes to splitting things up, but I think goal number one is getting all the information in there, then we can probably optimize the chapters more easily.

@ron Oh, and yes of course we must create a data driven TreeView etc 🙂 hehe.. I will definitely do that, but I need to focus on getting the guide done first!

Actually I was thinking about this, but would Fragment be a good fit in a datagrid?

@ron It is more expensive for sure, but no problem at all 🙂

its a technique I used a lot with wicket

I'll add specific support for fragments and add that as an example in the guide as well 🙂

do you need specific support? is a fragment not just a node?

@ron Sure, it can be used by instantiating a fragment and returning the root node, but I though maybe we could make it even smoother. Not sure how yet, will look at it tonight

Now you would do

cellCache { MyFragment().root }

Come to think of it, the only thing we could do is accept a fragment as the return type, because you would probably want to pass the value into the fragment:

interesting I was thinking of

cellCache{MyFragment(it).root

Exactly.