Looking at the app now.

Your wordlist menu also suffers from the same mistake as the

button(graphic = imageview

issue. I just realized that I should have added special support for nodes inside of menu items as well.. hehe, will add it now. You should just change to using the

ImageView()

constructor for now.

Committed a fix for that as well.

@javafxpert Another small nugget: In the main class, we have a helper for calling

Application.launch

, so instead of

Application.launch(WordSearchApp::class.java, *args)

you can write

launch<WordSearchApp>(args)

.

No need to do the conversion into a java class object, and no need to use the spread operator to convert the varargs.

@javafxpert About your "//TODO: How best to use local image resources?" comment -> there is a helper to extract resources from the classpath, and even turn those resources into know objects like for example an imageview. You can define a menu item with a local image like this:

item("test", graphic = resources.imageview("/local/path/to/image.png"))

If the images in your

/resources

folder are to be available on the classpath you need to move them to

src/main/resources

. They will then be at the root of the classpath, so to create an imageview for

add_word.gif

you'd write

resources.imageview("/add_word.gif")

.

More nuggets: When you call functions in Kotlin and you only pass a function parameter, you don't need parenthesis for the function, so

override val root = borderpane() {

can be defined as

override val root = borderpane {

A common way to configure the initial window size is simply to specify a prefSize for the root of the primary view, so on the next line after borderpane you could add:

setPrefSize(800.0, 600.0)

.

You could also override

start

in your app class and configure the stage there of course.

Stage setting also helps with the window resizing operations coming from the OS like the handles at the corner.

@javafxpert What does the original

wgModel

look like?

Huh, I added a thumbs up reaction to my own comment instead of yours @carlw 😆

There, that's better.

With min size you can control the window to a minimum size. If you put min size on a root you can still shrink the window

That's a good point @carlw, I didn't think of that.

It comes up a lot because users expect the min sizes on nodes to hold up a window resize

I pasted the link to the class referenced by wgModel

@javafxpert Are you planning on putting all the code inside of the same view? In that case you don't need a model, just define the properties as javafx properties with our slick syntax:

If that's what you suggest

@edvin uploaded a file: Untitled

@javafxpert I always try to split the views into logical "modules" and use injection between them. But if the application mainly consists of a single view and is not like a large business application that might be overkill.

The model is complex though

I just always do it, because I've never encountered an application that is just done after the initial release. A year in, the thing always grows into a monster, and includes an email client or something 🙂 hehe

Yeah, the model is pretty complex. You could actually define the class as

class WordGridModel : ViewModel()

. That way you can add properties like normal, but you can also inject this into several views and have access to the same data. There is nothing more to it, really.

gotcha

@javafxpert If you don't care about getters and setters, and mostly use bindings, you can even skip

val rowsProperty / var rows

and just define

val rows = SimpleIntegerProperty()

. Nothing wrong with that.

@javafxpert We also support very similar syntax to do enable/disable of items, for example inside of an

item{}

builder you can do

enableWhen(!wgModel.fillLettersOnGrid)

or

enableWhen(wgModel.fillLettersOnGrid.not())

depending on taste/preference.

There is also a

disableWhen

so you avoid negating your properties.

disableWhen(wgModel.fillLettersOnGrid)

. That makes it more easy to read IMO.