[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [e4-dev] how to contribute to toolkit model ?
|
Il giorno 01/set/09, alle ore 12:14, yves.yang@xxxxxxxxxxx ha scritto:
I'm not sure to understand. In XWT is possible to use user defined UI
element without deploy ?
Yes, exactly. It is in my demo for e4 presentation.
I'm an EMF lover. I have used and will use EMF as much as I can. But
I'm not
blindly to use it anywhere. Typically, we have an eclipse modeling
project
for UI (named PMF) that relies on EMF. But EMF solution for
declarative UI
has more cons then pros from the industry point of view:
1. Introduce another programming APIs for dynamic aspect, not
traditional
SWT/JFace APIs
2. The Interface/Implementation/Factory pattern has a limited
benefice
for declarative UI in eclipse/e4 context
It reduces directly the extensibility and flexibility. 1
i'm not bindly to use it anywhere. but i'm bindly to use when i have
to manage data model and IMHO ui parts are data model.
Using emf not introduce another programming API but instead use the
same as the modeled workbench
The purpose of workbench is to manage the view part in eclipse. It
doesn't
deal with the detail content of each part. As said Kevin, in most of
case,
we don't need to touch it.
But for the content view of parts, it is different. We need to
handle the
events and manage the dynamic aspect all time by programming. So for
UI
programmer, he/she has to learn a new API, instead of SWT.
the use of emf formalize a standard way to access and interact with
your model. this mean to simplify the things. SWT is much more
difficult, no ?
You want to re-invent SWT/JFace?
peraphs i strongly believe that using other tecnology than EMF to
model the UI is an important missing for the future.
Please don't put everything together. We do need a modeling UI
solution.
PMF addresses this issue.
sorry Yves... my english is poor and probably i'm not clear enough.
PMF does not fit in the declarative UI stuff.
i've read the draft proposal and it stay on top of it. It serve to
design the "application logic" and the high level UI presentation. is
it correct ?
i , as developer, need a way to tell "hey i want a button there, a
label there, and an image 10px on the right" in an WYSISYG editor.
at runtime i would like to access the model of the UI in an easy way
and be able to modify it reflecting the changes to the ui.
XWT does it.
TM will do the same.
i would prefer to be able to use an already known way (EMF) to access
the model at runtime instead of using a new API (XWT).
that's all. :)
