I'm not sure what look you're going for here, do you have a sketch or something that illustrates how you want it to look?

E.g. for horizontal layout:

+--------+         +--------+ +--------+ +--------+ +--------+
Category |      |v| Section |      |v| |   Add  | | Remove | | Cancel |
         +--------+         +--------+ +--------+ +--------+ +--------+

Vertical layout:

+--------+
Category |      |v|
         +--------+
         +--------+
 Section |      |v|
         +--------+
+--------+
|   Add  |
+--------+
+--------+
| Remove |
+--------+
+--------+
| Cancel |
+--------+

And square set:

+--------+
 Category |      |v|
          +--------+
          +--------+
  Section |      |v|
          +--------+
+--------+ +--------+
|   Add  | | Remove |
+--------+ +--------+
     +--------+
     | Cancel |
     +--------+

Sorry, I'm not good artist

You'd only need any special code for the first case. The Vertical / Square set is basic/supported by default. You can arrange the buttons in any container you'd like below the fieldset.

Looks like you could use an HBox around the fields perhaps

Yes, I've seen in wiki, but I need something to re-use this fragment, depending on context, where it appearts, e.g. center, right, or bottom of border pane

Pass in a parameter or set something in the scope and deal with the layout based on that perhaps?

What are the `field`s? Another wrapper, that adds

Label

to underlying control as graphic, or is a some kind of container? I'd like to use them, 'cause they easily attach labels

The fields are a custom class that extends

Pane

and offers different layouts based on the orientation given and there is also a custom Field for buttonbars

But you need something wrapping around fields, since you have multiple fields in a single row in the horizontal example

You could create the form, then call an extension function that creates a layout wrapper depending on the passed in layout argument, and then render the rest of the fields inside there. You might need to add a separate button wrapper in case of your square set layout to make only the two first buttons appear in the same line

Actually,

Fieldset

is an open class. You can make your own version for each distinct layout even

Does

fieldset

preallocate width based on the orientation and maximum field size?

No

I think

flowpane

between

fieldset

and the

field

does something weird. At least it has fixed size in that case

You'd have to inspect it to see what's going on

This is the complete set of styles applied to form and it's children by the framework:

-.txt

Just added listeners for width property... I was mistaken.

fieldset

resizing works dynamically, that was another container that restricted maximum width of

fieldset

Aha 🙂

I can't set layout properties in

Stylesheet

, can I? I see no

flowPane

element there

E.g.

hgap

,

vgap

It seems that no one layout is configurable via

Stylesheet

How to check if a Fragment has been opened via

openInternalWindow

over some Node (e.g. inside HBox)?

@ValV If a View is to behave differently based on where it's opened I think the most robust solution is to pass that information into the view, either through the scope (preferred) or with a parameter. You could however find the parent of type

InternalWindow

if you really have to know that detail 🙂

Ah, I don't know how to pass data through the scope yet. As for the last variant: if the window is internal, its parent would be

Node

(

StackPane

), otherwise

Scene

, right? And I'm not sure how to pass parameter, if I call

openInternalWindow<CategoryControlFragment>(owner = thatNode)

You can read about scopes here: https://github.com/edvin/tornadofx-guide/blob/master/part2/Scopes.md

@edvin, thanks. I'd like to try Scope approach, but can't understand what's going on in the snippet from the wiki, exactly: what is the

PersonModel

class and how does it reflect the state of

PersonEditor

instance

Is this

PersonModel

used to store parameters. As far as I understood, it should be

class PersonEditor: Fragment() {
  val model: PersonModel by inject()
  ...
}

So the trick inside

editPerson

just creates two instances for

PersonModel

and

PersonEditor

classes and sets them up in a separate resource space, right? I.e. to pass parameters via a Scope, I must create some auxiliary class for my

CategoryControlFragment

to store some options?

Am I allowed to pass a

scope.collection

or whatever into another controller? I don't see why not, but it's complaining anyway