|Re: Sphinx proposal [message #602783 is a reply to message #602773]
||Tue, 09 February 2010 12:59
| Stephan Eberle
Registered: July 2009
> in the upcoming sphinx proposal
> -> http://www.eclipse.org/proposals/sphinx/
> I see some overlappings in Workspace Management and Eclipse Platform
> Extensions with the, also new, Modeling Team Framework
> -> http://www.eclipse.org/proposals/mtf/
> Could someone from the sphinx team clarify the scope and relation to MTF?
It looks we have missed to notice the MTF project and to relate it to
Sphinx. Sorry for that. But as we have just entered the proposal phase
there is still plenty of time to catch up!
The answer to the question wrt the overlap between the two projects
depends on the time frame.
Right now, i.e., given what will be included in the initial
contribution, I'd say the overlap is very little. The reason: both
Workspace Management and Eclipse Platform and EMF Extensions are
designed to support and manage models which are already present in the
workspace. MTF seems to be focussed on the question how different kinds
of artifacts (models, other src files, and editors) can come into the
workspace by obtaining them from different kinds of repositories (CDO,
conventional SCM, and P2).
We have however a certain level of support for comparing model instances
which each other which is based on EMF Compare. It is for now used
locally only but we plan to extend it so that it can be used for
comparing locally managed model instances with remote ones through the
Eclipse team interface. This is something which could be interesting for
MTF as well, and if so, we should see how we can set up a collaboration
In the future we plan to extend Sphinx in a way that it is not only a
platform for locally operating modeling tools but for modeling tools
supporting distributed teams. At this point, the question of how to
share model and other artifacts over which kind of repository will
clearly come into picture. So, the scope to Sphinx and MTF will then
overlap much more.
But there is an important thing to notice: the scope of Sphinx does only
overlap with MTF but with many other modeling components too (e.g. EMF
Compare). This is not a problem because Sphinx is not meant to be a
replacement for all these other components. It intends to reuse them and
to integrate them in a consistent way. In other words, the scopes will
for sure overlap but implementations shouldn't.
Having said that, MTF seems to be a very interesting perspective for
Sphinx in that Sphinx could become a future consumer of MTF. If you
agree with that, I could add an corresponding item to the "Relationship
with other Eclipse Projects" section of the Sphinx project proposal. How
Powered by FUDForum
. Page generated in 0.06196 seconds