I have code that was written before we had builders.

@gtnarg I have restored Java interop with FX.registerApplication(), it's back to how it was 🙂

I want a way to declare an adhoc uicomponent without having to subclass View or Fragment and override val root etc. Would be very handy for showing dialogs etc.

What would we call such an adhoc view?

@User uploaded a file: Fragments on the run

adHocFragment

?

The contract is that you must return whatever should be the root Node, but you can do whatever you want before you start building the root.

So this would be legal:

@User uploaded a file: Untitled

@ron Is

fragment

too generic?

we already have Fragment might be confusing?

That's right. What about

inline

?

Not descriptive enough..

inlineFragment

?

It's soo long.

element

?

inline is if I remember correctly a kotlin reserved word?

element is very generic 🙂

Yes.

fxelement

?

It's just as generic 🙂

but it clearly signifies that it belongs to tornadofx and not to for example sax or jdom (I think they have elements too)

same as fxevent 🙂

inlineFragment

is the best for now. Maybe a shorter/better word than Inline?

You can do

this += inlineFragment { ... }

as well 🙂

Semantically speaking I think

adhocFragment

is better.

And

adhocWindow

which will open a Window right away

Seems to be working exceptionally well. Dialogs for example is much easier this way, instead of dealing with those pescy ButtonType.YES == it callbacks.

I like

adhocFragment

@User uploaded a file: adhocWindow can be used for dialogs and commented: Easy way to create dialogs with custom content, using builders and no alien syntax.