Yep. Do you understand the issue, why it doesn't work like you hoped out of the box?

I thought I would take advantage of builders for some components and do the final layout with migpane. Looks like I can't mix that way

No, because the builders already make sure to add the components to the MigPane. But if the keyword "wrap" could be configured after the node is added, we can adapt for that. Can they?

wrap is one of the constraint string, it could be like this as well.

add(iv.root, "width 5%, height 100%, grow,aligny top,wrap")

Perhaps Migpane is easy enough to do layout without builders, but I miss the goodies of internal styling, listeners etc etc..

@devanand I understand, but can you change those parameters after a node is added to the MigPane?

No, I believe

What we should do here is make that a type safe thing.

Looking at the source code now

It also have type safe variant "add" method. We can build constrains like

add(iv.root, CC().width("10%").alignY("top").height("100%"))

I see. That's not type safe imo, but it's a start. We could add a much nicer API on top of this.

Its a complex layout, I think you already have seen this http://www.migcalendar.com/miglayout/mavensite/docs/cheatsheet.html

It's pretty straight forward this thing. When a node is added to the MigPane, it is associated with a CC instance (ComponentConstraints). This can be retrieved afterwards and even modified.

Hang on, have to deal with something, then I'll cook up a quick POC.

sure

@User uploaded a file: Untitled

This is a hack that allows you to specify ColumnConstraints in a type safe way. The problem with this approach is that since I couldn't find an easy way to add CC to a node which was added without them, I have to remove the node, create CC, then readd the node. Not optimal. If there is a way to add CC to a node that was added without, this would be a perfectly fine way to deal with it.

It would probably be better to add an interceptor to TornadoFX so that we could add CC automatically.

okay, I will give it a try, thanks much.

Sweet 🙂

It would be cool to make CC more type safe as well.

cc { width = 90.pct }

or better

yeah, I will try for that 🙂

Cool. If you find a better way than mine to deal with adding, this could be a nice standalone library to use with TornadoFX.

indeed.

I think interceptor in TornadoFX or change MigPane default add method to set an empty constraint rather than null are the only two ways. For now I can live with string based constraints

infix fun <http://Node.cc|Node.cc>(sCc: String) {
    val migpane = findParentOfType(MigPane::class) ?: return
        migpane.setComponentConstraints(this, sCc)
}

How do I refer to an image I have in resources from type-safe CSS? I'm using

URI.create("path")

but I don't know what path should I specify.

Assume

resources

is root and specify from there. If the image is

resources/image.png

, use

"/image.png"

@devanand I will see if I can find a way to add interceptor support.

Ah, that should be pretty easy.