shadskii / reactorfx Goto Github PK

In the class FxSchedulers, recommend renaming the function platform to fxThread. It will read better when used in a static import and will likely hold meaning even if you change the the internal implementation.

Hi
Just to let you know, this points to another project, in case this is not intended to be :)

hi

i have a simple senaio: i have a loop with (1000 iteration) and just i want to launch this loop aync, son i use jfxdialog, i launch this senaio in Task, onrunning event i show my jfxdialog and onsuccess or onfaild i close it, i see that jfxdialog is show after loop terminate !!! however i show it in onrunning event (normaly it show before loop start) , any explanation please

Dear shadskii,

thanks a lot for this great tool! I just discovered a minor thing:
in your README.md there is a missing 's' in the group-id:

compile "com.github.shadkii:reactorfx:1.8.0" //Java 8

... I was just struggling a bit, because I was simply copying this line ;-)
Greetings

Currently, this library consumes the most important information about the changes that happened in the underlying library

For example, if I have a dynamic tree whose children can be added & removed dynamically & I want to expose this information to a TreeView, each node needs to know what changes happened to the child ObservableLists & in what position. This position information can never be accessed because the library swallows this information & only emits a subset of the this important information

For eg., for ObservableList currently I can only get

1. A new ObservableList via Flux<ObservableList<T>> from(ObservableList<T> source)
2. Only the added elements via Flux<T> fromAdditionsOf(ObservableList<T> source)
3. Only removed elements via Flux<T> fromRemovalsOf(ObservableList<T> source)

Instead the user should get the full power of underlying *Change (ListChangeListener.Change incase of ObservableList) objects. This way user will know what happened & most importantly where in the underlying child Observable*

This has to be applied to every Observable* collection as the library should never hinder the user from getting the underlying raw information if the user needs it as my above example demonstrates it