| [ECP] Relation to Sphinx? [message #622479] |
Mon, 19 April 2010 11:02 |
|
Hi all,
I've read the recently announced ECP proposal
http://eclipse.org/proposals/emf-client/
and have the impression that there is significant overlap with the
Sphinx project
http://www.eclipse.org/proposals/sphinx/
One the one hand, the problem being addressed (Background section) looks
to a good part very similar:
ECP:
"Even though those frameworks significantly reduce the effort of
building entity-centric applications it is still a long way from an EMF
model to a running application fulfilling basic requirements..."
Sphinx:
"However, experience has shown that the matter of creating an integrated
modeling tool environment for a given modeling language means much more
than just putting existing Eclipse components together. What is still
missing is some sort of "umbrella" framework which provides the
necessary glue and guarantees that Eclipse components can be
consistently integrated in higher level modeling tool environments. As a
result, all effort related to this part needs to be spent repeatedly in
every modeling tool development project and makes that the latter
frequently become major endeavors demanding considerable investment..."
One the other hand, many of the proposed solutions (Description section)
just look the same:
ECP: <=> Sphinx:
---- -------
Model Workspace <=> Workspace Management
Model Navigator <=> Navigator View and Editor Sockets
Model Editor <=> Navigator View and Editor Sockets
Model Validation View <=> Validation Runtime Extensions
Model Commons <=> EMF Runtime & Eclipse Platform Extensions
Could someone from the ECP team clarify the scope and relation to Sphinx?
Given that we have already 60+ projects/components in the Eclipse
Modeling Project my feeling is that we cannot leave it to the users to
figure out the differences/commonalities and pros/cons for each of
those. New project proposals therefore should
1. Clearly explain the differences wrt to existing or already proposed
projects
2. Help to avoid unnecessary redundancy and overlap by considering a
contribution to existing or already proposed projects rather than
opening up competing paths
I'm personally ready to help you with that by providing all necessary
details about Sphinx and am open to a discussion as to how to align
and/or merge to two projects.
Anything else will result in that the "way from an EMF model to a
running application fulfilling basic requirements" will remain quite
long because it's just so long and confusing to choose the "right"
modeling components out of the vast pool of existing ones.
Kind regards,
Stephan
|
|
|
Powered by
FUDForum. Page generated in 0.03021 seconds
] 
Search
Help
Register
Login
Home
