Separating observable data structures out into a separate library?

[Mike Hearn]

Yeah, but my API is UI framework neutral. Telling people to use all of
JavaFX isn't going to fly. Besides, I know the framework was developed by
the JavaFX team but beyond that, why is it a part of the UI toolkit?
Shouldn't these APIs be a part of java.util instead?

On Tue, Sep 23, 2014 at 8:47 AM, Johan Vos <johan at lodgon.com> wrote:

> The Observable framework works as part of the whole JavaFX Platform on
> Android, see http://javafxports.org
>
> - Johan
>
> 2014-09-21 15:06 GMT+02:00 Mike Hearn <mike at plan99.net>:
>
>> Observable data structures are a useful and general abstraction, which
>> JavaFX deploys to great effect. Combined with the mirroring techniques I
>> posted about a few months ago I found them to be a good way of combining
>> background work and network-updated state with GUI apps.
>>
>> For this reason, they'd also be useful outside of JavaFX, like on Android.
>> So I have a couple of questions:
>>
>>    1. Are there license reasons why the JFX Observable* framework can't be
>>    used in for example Android apps? How does the JFX license affect this?
>>
>>    2. If the JFX observables framework could be separated out from JFX
>>    itself, would there be any appetite for a Java 6 compatible version
>> that
>>    resided in some separate mavenable library?
>>
>
>