Personally i consider it as

@postConstruct

@ron I'm not talking about the

init

block, but I'm talking about the fact that I need to run a function called

Component.init()

to make sure that a component enters the TornadoFX lifecycle correctly. This happens whenever you inject or find a component, but it won't happen if you instantiate it manually. In that case you'd have to call

init()

from the

init

block of your component. See? 🙂

@ron Or are you referring to when I avoid

init { with(root)

and do

override val root = build {

?

No I was referring to the first block of your reply

I think one should not instantiate manually in tornadofx

Always use find

I really like the override val root = builder {

When you code in CDI don't use new😇

And tornadofx is in effect a CDI framework

can you bind to the paddingProperty?

for example to a slider?

@ron Ah, I see. Yeah, I think instantiating a Fragment is an anti-pattern, and should be avoided. However, Per pointed out that passing parameters in the constructor is far more convenient than doing it with the

param()

delegate, but that's the best we can do for now I think.

@ron The JavaFX

paddingProperty

is no good for binding, since it represents an

Insets

object. The new padding properties I added can easily be bound to a slider though.

They should be

DoubleProperty

instead of

Property<Double>

though. Will change them.

I meant the paddingAllProperty

@ron That's supposed to solve that 🙂 I found some issues with it now, working on it. Will let you know when it's perfect!

@ron

paddingXXXProperty

should be good now.

@User uploaded a file: Untitled

@User shared a file: Post coming to my blog

@User uploaded a file:

@ron Nice post, Ron! Two small corrections: It's the

init()

function of the Fragment that is not run. The result is that it will not receive docking events, hence it will stay undocked forever. Fragments will only receive subscription events when they are docked.

but then if I override the init function of Fragment in ComponentView I have to call

super.init()

there

@ron Yes, that's right. No need for super though, as the

init()

function is not the same as the

init

block. It's a function that just happens to be named

init

.

updated the blog post will push it tonight when I am home

Sweet! We gotta do this more often, getting info out of the slack channel and making it available. I'll be sure to blog more as well.

I agree that is why I started doing it, tbh I often use blog posts like that to remember how to do something

you should see my evernotes 🙂

@gtnarg commented on @ron’s file https://kotlinlang.slack.com/files/T09229ZC6/F04A8F758SF: You could improve the post by renaming ComponentView to MyView as ComponentView sounds like it is part of TornadoFx when in fact it's not 🙂

Nice one 🙂