Separating observable data structures out into a separate library?
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?
Re: Separating observable data structures out into a separate library?
There is a java6 compatible version available as part of javafx-ports Tom Von meinem iPhone gesendet Am 21.09.2014 um 15:06 schrieb Mike Hearn m...@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?
