Separating observable data structures out into a separate library?
tom.schindl at bestsolution.at
Tue Sep 23 12:27:35 UTC 2014
javafx2 was an extra install on Java6 (and even some version of Java7)
so those classes can not be part of java.util. Even in Java8 this would
not have been possible because then JavaFx would have to be JSRed -
which is NOT - just grab IBM Java and notice that there's no JavaFX.
Internally the library is already jigsawed so the base is split out - I
think this structure is also inforced by the build system and because we
get jigsaw in java9 which will make people think in modules and not a
Java SE categories I think this will solve itself.
On 23.09.14 14:15, Mike Hearn wrote:
> 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
>>> resided in some separate mavenable library?
More information about the openjfx-dev