I assume coroutine channels: https://github.com/Kotlin/kotlinx.coroutines/blob/master/docs/channels.md

oh. i thought it was client-side pipelines with this https://netty.io/4.0/api/io/netty/channel/Channel.html

Hey, has anybody an idea how to get the labels top aligned in a fieldset?

@jschneider - is this what you are looking for?

Nope. I want Orientation.Horizontal. Just the labels should be top aligned if there is a text area as value

I think I have to add my own style sheet

Last Sunday, I started putting together a functional prototype for a hobby project in my spare time using TornadoFX. On Saturday night, I let some of my target audience sit down and poke at it mostly unsupervised, and it was very well received. Thanks everyone for contributing to this project!

@jschneider - like this?

Yep.

I am messing around with a style for "label-container"

To get the same result?

nifty

no clue, but at least you can hide it.

(See the start of the article that @pike put up)

Hey guys! Quick question- I'm trying to implement TornadoFX's SqueezeBox in place of a HBox I have, but the class is final so I can't actually seem to inhereit from it. Is this intentional? I'm trying to replace my

class Item : HBox()

with

class Item : SqueezeBox()

Do I have to wrap it within a VBox or something

I don't know the reasons for the closed class, but if you're looking for a workaround, I sometimes use the Properties or UserData objects to customize a class in order to avoid inheritance. For example, attaching a "currentPosition" property to a stock HBox instead of subclassing and declaring a field.

Hmm, interesting. I tried used SqueezeBox().apply which seems like it will work, so thank you! Would still be interested to know why the class is final, however. For curiosity's sake!

yeah. extension functions too can help avoid inheritance

classes are final by default in kotlin, that'd be my guess as to why

yeah but there are classes like App in TornadoFX that are open and subclassed on a regular basis

I've even seen @edvin use Sealed Classes

My guess is someone just forgot to add

open

, but there may be an actual reason.

I think I made it final just because I'd rather have people submit PRs or feature requests than to silently improve it themselves 🙂

I have no issues with opening it up if you need to @Shan 🙂

What are you trying to improve in SqueezeBox?

Oh, I'm not trying to improve it at all! I barely know how anything works around here lol. I was just wondering why it is final while the other nodes like hbox and borderpane are not, that's all

I probably don't need to extend it in my case I was just extending an hbox and tried to replace it with a squeezebox and ran into this issue