I

ll come up with some better cases to make my suggestions clearer or to determine if they're valid. I'll be on slack early tomorrow morning (my time)

Great Carl! Good night 🙂

Over the past few days, I took some time to write my first blog post in awhile: Kotlin for Data Science. I gave TornadoFX a mention at the end. I think tool development with TornadoFX is going to be instrumental if this idea takes off. https://twitter.com/thomasnield9727/status/792203624419954688

I've been down and out today and training another guy at work on TornadoFX. Not feeling great but if I'm better tomorrow, I'll continue the guide. I may just continue writing it either way. More fun than watching TV.

@edvin Here's the test case I'm working on. I add a Controller to a Scope that is referenced in more than one view. I set a value on the Controller and see it displayed I'm having a little trouble getting SecondProjectView to display, but this is basic TornadoFX that I have to learn and not scoping.

@User uploaded a file: Scope Test Case

You call find(SecondProjectView::class) but you don't assign it to anything :) Try this += SecondProjectView::class 😃

It would mean the same as this += find(SecondProjectView::class).root

And += is just a shortcut for children.add

@carlw: If you put the project name inside the scope (subclass it) you can pick it up from there inside the controller/view. Might be cleaner than exposing those variables.

And if you add a ViewModel inside the scope then we're really talking 😁😎

trying that now...i'm still learning the typesafe builders

@User uploaded a file: Calling find() in init{} and commented: Why can't I call find() at line 10?

Is ViewModel something I can inject in other Views so that multiple Views can share the same ViewModel?

I don't see any reason multiple views can't bind to the same ViewModel

If that's your question...

ViewModel cannot be injected, but it can be put in a Controller that can be shared by multiple Views. It can also be passed around manually/by value. If you want to inject a ViewModel I think you can just let it inherit

Injectable

and it should work with scopes out of the box. This needs to be tested but if it doesn't work I'm pretty sure it's just a line or two to make it so.

Basically, we could make ViewModel a component. That would give it injection capabilities and also support it being a singleton view Injectable. Actually, Injectable might need to be renamed to Singleton or something now.

I just committed an update so ViewModel is now Component and therefore supports scoped injection. It also supports being injected into other components if you make your ViewModel Injectable, like this:

class VM : ViewModel(), Injectable

Then you can inject a ViewModel into some other component:

@User uploaded a file: Untitled

Hmm.. this is actually incredibly neat. Thanks guys, this was perfect! I think this makes MDI more pleasant @carlw

Oh.. if you now have a

UserModel

and you want to us it in a Master/Detail setting. Just subclass it like

SelectedUserModel : UserModel(), Injectable

and inject it into both the Master and the Detail View, and possibly add a scope if needed. Wow, that's fantastically neat!

So if I understand correctly - the UserModel instance that is injected is based on the scope? (ie., different scope -> different instance)

@edvin none of these scoped objects are singleton since there will be >1 instance, right?

@edvin that last snippet is what I'm getting at...Basically, I'm looking for a new Fragment or View class to be created and immediately get all of its dependencies without having to pass around information which leads to a tight coupling and an extreme source of bugs. This is especially true as the scene graph and section of the program gets larger

@edvin Give the users the capability to work a new requirement by doing this

openModel(MyFragment::class)

with this