|Re: One Framework to bind them All ?! [message #545249 is a reply to message #545132]
||Wed, 07 July 2010 09:51
| Andreas Hoegger
Registered: February 2010
You are right there are already a whole bunch of kind of "similar" projects.
E4: The new release of Eclipse with a lot of deprecation cleanup, code
injection and workbench modeling. Promises to reduce the entry barrier
for Eclipse newbies. Scout will extend the e4 workbench model by its
component model and use injection to access services (the concepts of
Scout and e4 matches by 100%).
JFace Data Binding: An GUI only data binding SWT/JFace dependent. Since
Scout is fully GUI independent we are not making use of JFace data
binding in the framework part.
Nebula: A widget library. Your decision to use Nebula widgets in Scout
Riena: Of all the mentioned project Riena and Scout have the biggest
overlap. Both of them are projects to build whole application stacks
(multi tier applications). The overlap is mainly in the runtime part.
The Scout SDK (development environment) has more overlaps with the
RedView project. It depends on the project requirements what to use.
Sapphire: Sapphire is a project more on the DSL (domain specific
language) and declarative UI side. To not reduce the language scope
Scout does not use domain specific languages nor declarative UI.
Hope it helps
Werner Keil wrote:
> I was wondering, how Sapphire stands compared to all those various
> binding projects:
> - E4
> - Scout (has its own mechanisms for binding)
> - Rienna
> - RedView (based on Rienna)
> - JFace Data Binding
> - Nebula (based on SWT/JFace)
> I may have missed some, but as you can see, there's already a whole lot
> of them out there.
> Also those are scattered all across different parts of Eclipse,
> Platform, RT, Technology.
Powered by FUDForum
. Page generated in 0.09284 seconds