Then you could specify the RowConstraints and ColumnConstraints for resizing.

I haven't, but I will certainly have a look at that 🙂 It might make it easier for people to style the forms that way. The alternative route is just to support more layout constraints for the current inputContainer. Going that route would give me lots of insights into JavaFX layouts, and I'm kind of interested in that as I've contemplated creating a HTML5-like layout with support for media queries and display: none etc.

I found this post on responsive JavaFX layouts interesting. This author suggests mediating between HBox and VBox http://www.guigarage.com/2015/09/how-to-create-a-responsive-layout-in-javafx/

I haven't come across a responsive requirement for a JavaFX app as my work has been limited to the desktop. What I provide in my forms to adjust for resizing operations is a sensible resize policy. For example, resize a TextField rather than resizing a fixed Label.

Yeah, Hendrik sure knows that he's talking about. But my vision would be to create a whole new layout pane that would work as a

div

in HTML5 with flexbox support. This would be a huge undertaking however, but would make JavaFX future proofed against mobile development. With JPro entering the scene, that short of layout is exactly what we would need 🙂

Don't forget that we get some nice benefits with JavaFX dealing with widgets. With everything being a <div> or <section> in the web world, you need Bootstrap or Flexbox to effectively build a grid. In JavaFX, you can build almost any layout by wrapping up HBoxes and VBoxes and setting up the appropriate properties.

Yeah, so this layout would be to satisfy the kind of problems that needs to be solved on the web. There is a reason people don't use table, br and div for HTML5 layouts these days 🙂 hehe

Since JavaFX now heads towards the web, I expect this to be even more true in the coming years.

I hope more layout properties will be CSS styleable as well. For instance, having to set VBox constraints in code and everything else in CSS makes it harder to reason about a particular layout.

Possibly, but we're not generating a document with JavaFX. Speaking of Mobile, Apple uses Autolayout or Adaptive layout for its latest development toolkit rather than CSS. GTK3 is in line with JavaFX.

Cool. Gotta check that out 🙂 Need to rest the leg a little, back later 🙂

talk to you later

@carlw Btw, we might generate documents with JavaFX soon, look at jpro.io 🙂 That's a JavaFX rendered "page".

Try to minimize that page and it all goes downhill rather quickly 🙂

For me, the future of JavaFX will have more to do with a WYSIWYG than a particular syntax. Qt and Interface Builder (XCode) are much better experiences than Dreamweaver.

I guess. I kind of found interface builder to be rather archaic.. But with a little polish that approach could really work.

I like interface builder, especially the drag-and-drop that keeps the UI artifact in sync with Swift and Objective-C. The test environment -- hooking up devices and the simulator -- is pretty good also.

if you're a pure coder, you'll appreciate the WYSIWYG a lot less

@carlw Yeah, to me it is easier to look at a nice builder tree than a graphical representation, but both approaches are fine really. Both FXML and code based UIs have their strengths and weaknesses I guess.

@edvin right, and i know your framework supports both. See the latest TODO app in my branch. I've found FXML to be very portable. I know of FXML created 4 years ago by a pair of graphics designers that's still working without modification.

@carlw indeed, and that's probably the strengest pro for FXML - the ability to have designers work on the layout without interfering with the code. One of many strongsuits of JavaFX. We're standing on the shoulders of giants 👌🏻

Btw, I'm having a hard time consentrating due to pain, so I probably won't do much this weekend. It should pass in a couple of days though 👍🏻

i'll bet your glad to have the new laptop so you don't have to sit up

Oh yes, that helped a lot 🙂

Extremely happy with this machine, the best PC hardware I could find really, and very affordable.

@edvin take it easy and feel better.

Thanks @thomasnield :)

Finding quite a few gaps in Chapter 5 for the documentation on "Data Controls". Surprised I missed several of these items. Making edits right now.

I'm beginning to think the

SmartResize

policy material might be good for the appendix. It's awesome though.

I never anticipated TornadoFX getting as popular as it is now, and I think it will continue to grow in the next two years especially if JPro.io takes off. I think the evolution probably will not slow for awhile, and we need to rethink how we add to the guide and accept it is a living, breathing document that will evolve with TornadoFX.