|Re: Are draw2d objects turned into modeled objects? [message #756180 is a reply to message #756056]
||Fri, 11 November 2011 07:00
| Thomas Schindl
Registered: July 2009
Am 10.11.11 18:03, schrieb Mickael Istria:|
> Hi all,
> As far as I understood, e4 is based on the idea of a fully modeled UI +
> a renderer. So that, from a customer point of view, SWT does not exist
> anymore, but instead, we have a model that is then rendered with SWT.
Yes but the rendering stops a the Part-Bounderies so inside the
Part-Instance you'll have to decide in which UI-Technology you are
running and your (SWT)Java-Code is executed. All the framework passes
you is a part you can draw your self on (for SWT a Composite, for Swing
it would be a JPanel, for JavaFX a Parent, ... => this belongs to the
rendering engine creating the workbench layout).
If you want to see none SWT in action I can point you to:
who implement the rendering using JavaFX, but naturally then one also
has to implement the inner stuff using JavaFX as well.
The code in https://github.com/tomsontom/emfdatabinding-tutorial is a
bit older but you see there the same UI implemented 3 times. I've
started long ago a project called UFaceKit which would all to write such
forms once and run under different UI-Systems but that didn't made to
> The compatibility layer turns SWT code into a model.
> Am I right so far?
The compat layer translates extension points like view, editor, ... into
model elements but not SWT.
> If yes, then my question comes to draw2d. Has the same trick be
> implemented for draw2d ?
I'm not sure about which trick you are talking here. draw2d is normally
only part of the area Eclipse 4 has handed over control to you custom code.
> Thanks in advance.
Powered by FUDForum
. Page generated in 0.02299 seconds