[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Newsgroup Home]
|
[news.eclipse.platform] Re: [Databinding, General UI] UI brainstorming, (nearly) all stolen ideas
|
Boris Bokowski schrieb:
> We had a good discussion on the topic of using modeling for UIs at the
> Eclipse Summit Europe 08. What I took away from that discussion is that
> there are three areas where modeling makes sense:
>
> 1. At the widget level, where you would have a 1:1 mapping between the
> widgets and objects in your model. XSWT and XWT are in this space, as is
> Olivier's wazaabi 2. What I find important is that at runtime, you don't end
> up with twice as many objects, so being able to directly create widgets from
> a persistent representation is important. At the same time, having EMF
> objects that are again 1:1 mapped to SWT widgets is interesting for tooling
> purposes, so maybe what we should do is have a persistent format for SWT
> widgets, which can also be read in to create EMF objects if you are in
> "design mode".
>
> 2. At the application level, where you don't model the innards of your UI
> components (views, editors, ...) but you model how those components are
> glued together. An example of this is Application.ecore/Workbench.ecore in
> e4 (see org.eclipse.e4.model.workbench).
>
> 3. At an abstraction level higher than (1), but still concerned about
> "inner" UIs, are things like the proposed PMF project
> (http://www.eclipse.org/proposals/PMF). The idea here is that if you have a
http://www.eclipse.org/proposals/pmf/
Tom
--
B e s t S o l u t i o n . at
--------------------------------------------------------------------
Tom Schindl JFace-Committer
--------------------------------------------------------------------