You want to decouple correct?

That is what the

CompositeObservable

is for, which I'm planning to be the last chapter

one of the reasons I really like to use guava eventbus is because I can just subscribe to an event

Yeah,

CompositeObservable

is like an event bus, although I'm still debating some refinements to it.

I am eager to get your guys' input on it. Essentially the idea is you create a Model/Controller class holding all the CompositeObservables. Sources plug into it, and Subscribers subscribe to it. I've been using it heavily for some applications at work and it has been working great. But I think it needs a few more options, and debating how configurable I want to make it.

I would also be interested in seeing how this could be used in recursive methods

Oh man, Rx and recursive... you can do some crazy things if you have a need for it. Haven't explored that area much but I've done a task here or there.

the example with the up and down button is an infinite observable

maybe note that?

That is true, I'll call that out.

in the kotlin part could you not use

ListOf("Dallas","Houston","Chicago","Boston").observable()

instead of

FXCollections.observableArrayList("Dallas","Houston","Chicago","Boston")

Oh, I keep forgetting about that extension function. I'll do a sweep later and replace those. Thanks!

chapter 6 is quite good,

is that contrived example really needed? For me the other examples make way more sense

You might be right. I might have given

Binding

excessive coverage, and that did occur to me earlier. I'll go ahead and remove it.

and the code for lazybinding in java is different then the code for kotlin

@User uploaded a file: Untitled

I am not certain but the

toLazybinding { it.printStackStrace()}

feels strange

Good eye

in the java part you dont have the onError

Yeah I realized that last night. Let me remove it for consistency, although you should use

onError()

when putting Rx code in production

But I didn't want to distract from the concepts

but dont you need to name the onError?

toLazyBinding { it.printStackStrace()} feels like its being bound to the stacktrace

Hahahaha, okay that is the first time I heard that but I can see your point

I'll tell you what, I don't know if we can fix that with RxJavaFX, but RxKotlinFX we can leverage a builder to alleviate that

This is the kind of stuff I want input on before 1.0 release, so glad you are sharing

you understand my concern?