@thomasnield That is exactly right. I look at just a typical selectionmodel, which is one of like 10 classes for this grid component. In JavaFX a typical implementation is 1000 lines for some reason, and my whole grid with the selection model is 500 loc. I probably simplified too much though.

I did however improve upon some areas compared to the JavaFX data driven controls. I'm using a lot less listeners and instead do a little more work when selection changes. It sounds like a less wasteful approach, and probably uses a lot less memory.

Not to sound all "Microsofty", but making it exclusive to the TornadoFX platform not only allows you to maintain it on your terms (e.g. in Kotlin), but also gives TornadoFX more reason to be used. It also points out the benefits of the Kotlin platform if its much easier to use from an API perspective and is more maintainable.

@thomasnield Yes, absolutely. And as I always like to say: You can use whatever parts of TornadoFX you want. You can just include Kotlin and TornadoFX in your plain old JavaFX application and start using this grid view. So there really is no down side to it IMO.

@thomasnield I really liked that I could finally make

cellFormat

and

cachedGraphic

first class citizens instead of extension functions. Felt good 🙂

The way the grid is set up you could even using it in plain Java

There is a gridview in controlsfx but less performant then this one

Also you need way less code with tornadofx

I would change the name of cacheGraphics as it is not just for graphics

I read the tickets in controlsfx concerning the selection model there were no technical issues not implementing it only licence issues

Yeah, I don't like the name

cacheGraphics

either. The point of it was that the result of that call will be set as the cell`s

graphic

property. We need to rename that thing before I can do the screencast.

cellCache

?

Something like that, yes!

Better symmetry vs

cellFormat

as well.

Been doing some incremental copyedits to TornadoFX Guide. Also added more content including covering

rowExpander()

. I'd like to review type-safe CSS chapter in the next day or two since that has been somewhat incomplete for some time.

Need to cover mixins and all that.

Which honestly I have to wrap my head around again. I understood it at some point but then forgot since I'm not a heavy user of styling, except for pragmatic purposes.

But type-safe CSS works wonderfully with Rx to keep conditional formatting updated.

I never really got into the whole CSS thing

I just use bootstrap or sekeleton if I needed something like that

btw @edvin my drag&drop code works real well with the datagrid

@ron Cool! Hopefully we're on the right track with it. I'll let you know when I change the name to

cellCache

later today.

Woudl be cool to test it with maybe 1000 image url's or something to see how it performs..

I can do that

I have a directory with 4800 images in it

holy f*ck its close to instantanious

one thing could be improved I think

when changing the backing list, the index is not reset

Haha, cool! What do you mean the index is not reset? Selected index?

the selectedIndex