(thanks for the tip on the vgrow, that's a much better solution)

@carlw I know you like GridPane, but I think we can get several valuable other benefits from creating a custom layout manager. I'll solve the Form issue first though.

I wouldn’t mind a different abstraction on top of GridPane…The stuff I did with Form hides that from the developer My Form implementation was staying away from Pane and attaching listeners to resize everything…I didn’t like that either

I’d like an API val grid : Grid(12) grid.add( Label(”HelloWorld”), SM ) grid.add( Button(”Press Me”), SM )

Good point. I will definitely take a closer look at that approach when I get to the Form thing. So many small details to land first though 🙂

Maybe a Row would be intuitive val grid : Grid(12) val row : grid.addRow() row.add( Label(”HelloWorld”), SM ) row.add( Button(”Press Me”), SM ) row.add( TextField(), LG )

With adding handlers to width and height, I worry about the screen jumping around as JavaFX takes a turn resizing everything, then the listeners go

That's not good enough. Validation errors will toggle classes on the field container etc, so this is too simplistic. Do you have issues with the current Form implementation concerning flickering/jumping?

no

i haven’t done any validation with TornadoFX. are messages added to the scene graph?

Yes they are 🙂

I think I made a screencast about it and it should be in the guide.

Validation combined with the ViewModel is pretty nice.

i have a lot to get to with TornadoFX…my suggestion for Grant's #190 is more specific and retains the existing API for the user (Form/Fieldset/Field). For this type of UI requirement, I’d use a one (vertical) or a two (horizontal label) column GridPane and pass along Grant’s resize specifier to the RowConstraints.

I think it's a very small issue to support the row constraint within the existing Field implementation, so I will definitely implement that, but if you want to work on the GridPane version we can compare notes in the end?

@carlw I agree about getting up to speed... With work, my wife's small business and two teenage boys it's hard to spend the time I want. But it seems like an amazing framework. Slowly but surely I hope to port/create more applications using it...

@edvin. sounds good. it looks like the scope stuff is well taken care of. I’ll continue with the XForm/XFieldset/XField (named with “X” to live alongside the Form/Fieldset/Field version). Being able to implement this in Kotlin will help me learn the language even if you go another direction

Perfect @carlw 🙂

@jchildress Happy to hear it. And we're here when/if you need help 🙂

@edvin what is The difference between no-nn and no-nb?

And which one is commonly used?

For swing - I'm a big fan of DesignGridLayout - my goto for laying out forms - simple api yet powerful - based on canonical grids. You might want to read through the docs as a source of ideas/inspiration.

@ron nb=Norwegian Bokmål (book language), nn=Nynorsk (translates to "new Norwegian" but is actually more like "old Norwegian". Less commonly spoken in central places of the country. Large parts of Norway speak some kind of dialect, but Bokmål (nb) is the common form. We learn Nynorsk in school though, and it's pretty easy to understand when you know Bokmål.

@gtnarg Thanks. Have you tried MigLayout? I used it for Swing and I think it's available for JavaFX.

I've tried it - and was actually a bit disappointed. It's powerful - but compared to DesignGridLayout it's not simple. A good analogy is comparing TornadoFx to JavaFx 🙂

@gtnarg Ah, I see 🙂 We'll add a better grid layout soon 🙂

@edvin - I think you are already very close with form - just needs a bit of tweaking.

@gtnarg My thoughts as well 🙂

@edvin woden ha du da. you forgot about no-ob norwegian