@edvin I’m getting a build error from the latest kitchensink. I ran a mvn install on the TornadoFX project and updated the kitchensink gradle beforehand

93729 AM: Executing external task 'build'... e: /Users/carlwalker/Desktop/git/tornadofx-kitchensink/src/main/kotlin/tornadofx/kitchensink/samples/alignment/view/MainView.kt: (84, 18): Unresolved reference. None of the following candidates is applicable because of receiver type mismatch: public fun Node.style(append: Boolean = ..., op: InlineCss.() -> Unit): Unit defined in tornadofx e: /Users/carlwalker/Desktop/git/tornadofx-kitchensink/src/main/kotlin/tornadofx/kitchensink/samples/alignment/view/MainView.kt: (85, 13): Unresolved reference: backgroundColor e: /Users/carlwalker/Desktop/git/tornadofx-kitchensink/src/main/kotlin/tornadofx/kitchensink/samples/alignment/view/MainView.kt: (85, 29): Unresolved reference: += e: /Users/carlwalker/Desktop/git/tornadofx-kitchensink/src/main/kotlin/tornadofx/kitchensink/samples/alignment/view/MainView.kt: (87, 25): Type mismatch: inferred type is Dimension<Dimension.LinearUnits> but Double was expected e: /Users/carlwalker/Desktop/git/tornadofx-kitchensink/src/main/kotlin/tornadofx/kitchensink/samples/alignment/view/MainView.kt: (88, 26): Type mismatch: inferred type is Dimension<Dimension.LinearUnits> but Double was expected e: /Users/carlwalker/Desktop/git/tornadofx-kitchensink/src/main/kotlin/tornadofx/kitchensink/samples/alignment/view/MainView.kt: (89, 23): Type inference failed. Expected type mismatch: inferred type is CssBox<Dimension<Dimension.LinearUnits>> but Insets! was expected :compileKotlin FAILED

@carlw Yeah, the json structure was great! Thank you 🙂 You need to pull and install tornadofx, since I added the

Collection<Node>.style

call to support the

children.style {}

thing.

I see. I missed that commit from 2 hrs ago

Hehe, sorry about that. I wanted to bring

style

in line with

addClass

, which also supports adding to a collection of items in one go. Actually, it should have been Iterable, not Collection. I'll update it.

There, committed 🙂

@edvin you’ll need to pull from me too. just testing on my mac and we have to wrap the tilepane in an anchorpane to make sure that the 3x3 grid shows up

@edvin out-of-the box, the screen was wider and flowing an uneven row/col structure

Ah, sorry about that. But can't you just set minWidth instead?

no

@carlw I added you with write access so you can commit it 🙂

Doing homework with my daughter. Back later!

np. thx…new commit is simple anchorpane{} around tilepane{}. even with minWidth, i think the container is stretching out the horiztonal contents

i’ll check out maxWidth before i push

maxWidth will work too. i think the anchorpane{} wrapper is less brittle since i have to compute the maxwidth from the vbox widths x prefColumns plus padding and gap

Ah, sorry, I meant maxWidth 🙂 And I agree about brittleness.

i don’t have write access to i wrote a PR for you

NVM...I didn't accept the invite

Change is merged in

Haha, sweet 🙂

@thomasnield I was looking at the CSS chapter in the guide to see if we described inline styles anywhere. I can't find the word "inline" in the guide, but maybe you used some other word to describe it?

I think I did inline, it was the first topic in the chapter wasn't it?

Let me check.

Haha, I searched for inline styles, not inline CSS 🙂 Sorry! I will add info about the new

Iterable<Node>.style { }

option I added today.

Interesting, I want to check that out...

Pushed a change now 🙂

Some times you want to apply the same styles to many nodes in one go. The

style { }

function can also be applied to any Iterable that contains Nodes:

@User uploaded a file: Untitled

The

fontWeight

style is applied to all children of the vbox, in essence all the labels we added.

I also updated the example where you filtered and added classes to include an example using the

Iterable<Node>.addClass()