@edvin the architecture was to connect to a well-known, central server then hand off to a peer-to-peer design

Nice. I've actually already done all the work for the properties, I use WebSockets in our Backup Client software, which is integrated with our CRM. It would be pretty easy to generalize it.

websockets are awesome...just a few annotations on the serverside. on the client side, i was using Netty

I'd probably go with Netty this time around as well.

I'm using Tyrus.

Your fxcheckers is Java not kotlin😞

The Expanse Season 2 is pretty good so far, btw.

@ron no, but we're identifying a use case

@ron If i convert my half projects to Kotlin, they'll end up as quarter projects

Haha 🙂

At least in terms of LOC

what is the current "right" way to have pojo's in columns?

currently I use

class ExifPane : View() {
    val controller: PhotoController by inject()

    override val root = tableview(controller.taglist) {
        column<Tag, String>("name", "tagName")
        column<Tag, String>("value", "description")
    }
}

I'd do

column("Name", Tag::name)

no the code does not like that

@User uploaded a file: Untitled

Ah, and old fashioned Java POJO.

column("Name", Tag::getName)

nope thats the error I just posted 😉

Tag::name

and

Tag::getName

gave the same error?

if I use

Tag:tagName

I get

Error:(44, 29) Kotlin: Unsupported [reference to the synthetic extension property for a Java get/set method]

Maybe just use your initial code for POJO's then 🙂 The type safe alternatives become quite verbose.

also the squeezebox does not fill the complete length

Inside what?

A Drawer Item?

@User uploaded a file:

yes

It probably should. I'll take a look at it 🙂

isn't is just 'column<String>("Name", Tag::name)' ?

see the first error message I posted @gtnarg

It doesn't work for getters defined as Java code it seems.