|
|
|
|
|
|
|
|
|
Re: Remote UI [message #1052580 is a reply to message #1052559] |
Tue, 30 April 2013 09:04 |
Eclipse User |
|
|
|
Vaaclipse is an OSGi runtime on the server, which, for each user/workbench holds the EMF model, does the rendering in Vaadin widgets and serializes the javascript widgets (they get converted java-to-javascript using GWT) to the browser which renders them using its javascript engine. I'm not sure I understand the usecase of having a native JavaFX client communicate with the "server-side" part of vaaclipse. If nothing else, the e4-JavaFX client will have its own OSGi runtime. If the goal is that the vaaclipse and JavaFX client have the same data source then that's something else.
Both of these are front-end solutions, which means they are parallel and in front of a data source which can be anything, from a database to files, a web service etc. I don't see vaaclipse server-side(or RAP for that matter) as a producer and the JavaFX client as the consumer.
If you want to have them communicate in terms of visual sync then remote OSGi comes to mind. As long as you have access to the EventAdmin of an OSGi runtime then you can sync visually because all visual manipulations go through the event broker.
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05232 seconds