@Ruckus We got an issue for the css support. I think you're best suited to handle it if you have the time 🙂 https://github.com/edvin/tornadofx/issues/203

@Ruckus Actually, two from the same guy 🙂 If you don't have the time then I'll try to figure it out.

@edvin so you can use scopes to inject several managed instances, rather than being restricted to a a singleton? I was going to ask for this once I knew how to frame it..

If I have a

View

tethered to a specific

Scope

, is there something I can hook onto for teardown operations? This may open up some new reactive patterns but I'll need to make some more features for

CompositeObservable

Scopes are a good idea, very natural progression.

@thomasnield That's right. I'll show you in "tonight's screencast" 🙂 There is a

scope.deregister()

call you can use for the teardown.

Interesting okay, looking forward to it. I've got some new Rx patterns to sort through. I need to figure out how to kill reactive broadcasts for a UI that's been disposed.

I think I figured out how to accomodate this on the Rx front.

@edvin Got them, thanks

@thomasnield If you're looking for other looks on the scope concept, read up on ConversationScope in Seam or Stateful Session EJBs. There is an end user responsibility in marking the end points of the scope's lifecycle.

@thomasnield I'm looking at RxJava as an addon or better integration with TornadoFX for MVVM. It looks like binding and ViewModel cover a lot of it, but I've been reading about a "back channel" notification that reverses the V -> VM -> M communication. Microsoft uses some extra property notification objects called INotifyPropertyChanged to get the View to respond to something in a decoupled manner. From the Microsoft docs "Implementing the INotifyPropertyChanged interface allows views to react to changes originated in models and view models. These changes are not limited to domain data shown in controls; they are also used to control the view, such as view model states that cause animations to be started or controls to be disabled."

That sounds like it has Rx written all over it

I modified the

CompositeObservable

to be backed by a

Subject

instead. Adding an

Observable

source to it will yield a

Subscription

, which you can call

unsubscribe()

at any time to stop sending emissions. I think this will effectively decouple Observables and Subscribers throughout models, views, controllers, etc whatever your setup is, and allow removal at any time.

Microsoft pretty much invented ReactiveX.

The case for this that comes to mind is a View with a SwingNode. The contents of the SwingNode won't be bound easily to the ViewModel. It's probably better to have the "back end" fire off an event to refresh the SwingNode rather than try to build out a set of JavaFX listeners and properties for JTextField, etc

Push-based event notification does make things drastically simpler, especially as things become more asynchronous

Part two is here 🙂

@thomasnield Hopefully a screencast a day will keep the doctor away 🙂 How are you feeling today?

@edvin Awesome, I'll watch it today! Doing better, I'm on some stronger antibiotics and its finally knocking it out. Been dealing with this for a week so I'm ready to be done. I've been using the time to read up on stuff and catch up.

@thomasnield Good to hear 🙂

@edvin Nice

@edvin Just watched the new screencast. Very nice. Great job!

@thomasnield I answered him

@Ruckus thanks! Testing now

@voddan Hah! I didn't make the connection it was the same voddan 🙂

Even with the same picture and everything

@edvin Another question: I have a

ListView

which displays nodes from an ObservableList with a

cellFormat

. All good. But now I also need to know the indices of the elements in the list for

cellFormat

to show the data.

How am I supposed to do it in Tornadofx?