(Slackbot says the workspace is out of storage. Let me know if you don't see two screenshots above.)

I see them. We’ve been getting that error over the past year but it doesn’t seem to affect postings to the forum.

@ianbrandt your filename says “fixed”. Are you up-and-running? One note, you should prefer this override val root = vbox { button(“Press Me”) } to what you have so that you can use the more concise builder style. Also, declaring the whole scene graph in the root definition (instead of the ini{}) keeps the flow together

@edvin Here's the project, in case that's of any help: https://github.com/ianbrandt/tornadofx-test

@ianbrandt It's because you're missing the

tornadofx.*

import

So it doesn't see our

plusAssign

extension

If you look at your second screenshot, the IDE added the correct import.

Somehow it didn't in the first example

@edi

@edvin Ah, I see what's going on. I have Preferences > Editor > Code Style > Kotlin > Imports > Top Level Symbols set for "Use import with '*' when at least 5 names used". I believe that's the default. When I switched to

launch<MyApp>(args)

that put the

tornadofx

imports over that threshold. I've since installed the TornadoFX plugin, and it seems to have added

import tornadofx.*

to the "Packages to Use Import with '*'" list, so that would avoid this scenario going forward.

@ianbrandt That's right, this is one of the small tweaks the plugins makes to your config 🙂

This is needed for a lot of different gems in TornadoFX 🙂

@edvin @ianbrandt I think the docs should remove the init{} example and present the builder syntax right away in this page https://edvin.gitbooks.io/tornadofx-guide/content/part1/3.%20Components.html A later section on the same page does present “a brief intro” to the builders, but it’s not the same example (different scene graph). I think the builders are a key reason for using TornadoFX. Otherwise, you’ll have a lot of JavaFX object manipulation to do.

@carlw I completely agree

I’ll create a PR to consolidate the “first app” with the “brief intro”

beginners will end up with a lot of val b = Button(“Press Me”) root += b b.setOnAction( { ….

@ianbrandt are you coming into tornadofx with a javafx background?

@edvin I think a callout in the guide that

import tornadofx.*

is a must would be good too. I've seen shops enforce the "Use single name import" setting. (Makes it clearer when a class has too many dependencies.)

@carlw No, haven't done any JavaFX before now. A lot of AWT and Swing in days gone by.

ok. i wrote a PR to consolidate the section you’re working through with the later section on builders

Thank you @carlw 🙂

@ianbrandt Good point!

This was an interesting learning experience about Kotlin DSLs and

import .*

in general. Going to have to remember this one. 🧠

@ianbrandt @edvin If I work the issue I just wrote up, do you think this will be a better “hello world” for the leadoff of Section 3 “Components”?

@carlw Actually, I think a literal "Hello, World" example with a label would be the best first example. It's kinda the industry standard, and it's what I was first looking for. But, I think that's a great second example!

ok. two examples might be even better. a first example that’s vbox{label} and then mention the builders and present a second example with the action thrown in highlighting the syntactic value of the builders (vbox { button { action)

@ianbrandt uploaded a file: TornadoFX Hello World

I'd put the import in the examples too, or at least the first couple, just to drive that home.

@ianbrandt Great, I'll add that also

I've updated Chapter 3 to use only builder syntax, made some improvements to explanations and also mentioned the

tornadofx.*

import