|Re: Any plan for a JavaFx implementation ? [message #1724631 is a reply to message #1724511]
||Wed, 24 February 2016 23:25
|| Vincenzo Caselli
Registered: January 2012
Hi Vincent, Aurel, Krisztian,|
wow, it seems this one is a really needed feature.
The good news is that recently we have indeed decoupled the UI and the Core parts of EMF Parsley.
You can know more details watching our latest EclipseCon talk
(from about min 22:00 for this specific feature)
In this case we use the Parsley Core inside a JEE Servlet (so in a pure Java environment) and provide a JSON communication with virtually every kind of client (we made implementations for a traditional web UI in AngularJS, GWT, but also mobile, both native Android and hybrid). So in practice we allow a communication between two tiers: a generic UI and Parsley core.
What you are asking is indeed something easier because in the case you are referring there's no need to use a cross-communication protocol (like JSON); basically both ends are in the same Java instance.
In the end you can use the Parsley Core API and get data along with UI customization info (both following the Parsley customizations) that can be used to render the UI.
The cons are that the specific basics UI parts must be set up in the specific language and that some mechanisms like UI databindig, listeners, drag&drop, etc... are not included as in SWT or RAP.
You can see an example of EMF Parsley core API usage here:
So in the end: at present there is not available an out-of-the-box solution for JavaFx, but we are working to make EMF Parsley more and more decoupled from UIs.
We will keep this thread updated with further steps.
Powered by FUDForum
. Page generated in 0.01480 seconds