@edvin No your got that right I want to put the config property in the app class for the global config. And the enum is also in the config object. But I was thinking that you could also write to the global file from a component like this:

kotlin
   config(GLOBAL) {
       set("Global-Key" to "some-value")
   }

Which would allow all components to use some commen config together and for that the component would have to have the ability to access the global config property. So the question would how I acess the global config form the

config(GLOBAL)

function. Dose that make sense?

I'm following the book trying to learn this, because it seems like a nice way to work with JFX

And I'm catching a snag on the Controllers section.

Ah, nevermind, was my fault

Seems that the inject() delegate can only be used on val properties?

The code itself works, but the action block that is shown in the book doesn't actually compile in IDEA

I need to use setOnAction

Was this an API change?

@redrield Hey! Yes, injected properties must be declared as val. We recently added action as an alternative to setOnAction, it will be in TornadoFX 1.7.1 which will be released this week. Sorry, was not aware that we had updated the guide to the new syntax yet, I guess we jumped the gun a little on that one :)

@edvin That's my bad I updated the guide... but maybe we should start having a snapshot branch so. We can update the guide to keep it in sync with the code and then merge it during the release?

This would prevent the guide to be ahead of the release ....If we would only make improfments to the guide not regarding new snapshot changes we would still make those on master .

@nimakro are the changes you are making to

config

not getting close to mimic the behaviour of

java.util.Preferences

?

@edvin I like the new JSON methods and I am going to try them in kphoto 🙂

@ron yeah, your probably right

hi. I am new to tornadofx And I can't figure out how to open a new separate window (modal or non-modal) 😞 Looks like

openModal

does not accept view as parameter

Hi @alexp11223

openModal

and

openWindow

operates on an instance, so you can instantiate a view and show it using

find<MyView>().openWindow()

for example.

Or even

val myView = find<MyView>(); myView.openWindow()

.

On two lines preferably 🙂

@ron Sweet, let me know how they work or if we can make them even more convenient.

@nimakro This is the first time it has bitten us, so let's not worry about it for now. I'll do the release in a couple of days so we're up to speed with the syntax in the guide.

ah. yeah.

find

? Can't I just use

MyView().openWindow()

? What are advantages for using

find

?

@alexp11223 All views and fragments are instantiated by the framework, not by the user. This way all plumbing that needs to be done is done by the framework

This is a blog I wrote about that: https://ronsmits.org/2017/01/tornadofxcdi/ maybe it helps

btw looks like

find

always retrieves the same instance (singleton). What if I need multiple instances of a view?

then dont make it a

view

make it a

fragment

like the post says: Allthough very cleverly hidden TornadoFX is in fact a CDI framework. Instantiating a Controller, viewModel, View or Fragment using the find or by inject pattern will tell TornadoFX to either create the requested instance or (except for Fragments) find the one already instantiated.

@alexp11223 What @ron said 🙂 You can also keep it a View, but open it in a new scope. You should read about scopes in the guide before going that route though.

grins I have not found a use case yet for scopes 🙂

I use it a lot 🙂

hm. I saw in the guide usages of

button { action { .....

https://edvin.gitbooks.io/tornadofx-guide/content/3.%20Components.html but now only

setOnAction

works. Was it renamed? Why?