We decided to go for JavaFx as it is more promising than we initially thought. Besides native desktop clients it can potentially lead us into the mobile world. Further we also want to create a web implementation based on javafx that offers a bridge to the browsers DOM and to the JavaScript world. That is all we need to make it possible even though it will still be very tough. In comparison to the GWT implementation this will require the java(fx) plugin available in the browser but therefore our client code is executed a true java so we skip additional compilation and all the limitations of GWT.
We decided to go for JavaFx as it is more promising than we initially thought. Besides native desktop clients it can potentially lead us into the mobile world. Further we also want to create a web implementation based on javafx that offers a bridge to the browsers DOM and to the JavaScript world. That is all we need to make it possible even though it will still be very tough. In comparison to the GWT implementation this will require the java(fx) plugin available in the browser but therefore our client code is executed a true java so we skip additional compilation and all the limitations of GWT.