Pierre,
Comments below.
On 04/10/2013
12:49 PM, GAUFILLET, PIERRE wrote:
Hello PMC!
As some of you already know, the members of
TOPCASED are gradually migrating components to Eclipse /
PolarSys projects.
Yes, that's great!
In this context, I am currently considering the
case of our cross-ref view (see https://polarsys.org/wiki/index.php/PolarSys_Improvements/TOPCASED_facilities
for information about this functionality),
The wiki doesn't provide any
architectural details about the source code. Just a comment
about "This code derives from Ecore Tools, but works for any
EMF model" so I'm not sure about the details of the actual
code dependencies; if the dependencies are something other
than purely the EMF Core SDK, then it's not a good fit for
the Core SDK, though potentially could still be in a
separate SDK-like feature, much as Xcore is in a separate
feature that has Xtext dependencies...
[PGa] Right. Here is the list of
dependencies:
org.eclipse.core.runtime
org.eclipse.emf.ecore.edit
org.eclipse.emf.edit.ui
It exports an extension point in which you
can contribute specific behavior for given editors (GMF,
Papyrus, etc.) and cross-ref filters matching specific
meta-models (UML, ecore, etc.). I expect to contribute
at least a extension plug-in for GMF for now.
and wonder what is the most appropriate project
for hosting it. At first sight, reasonable choices may be:
- EMF, as this view works for any EMF model
Yes, though it depends a
little bit on how general this is as well as the
dependencies. I imagine you can't do an effective search
without some kind of indexing strategy and when it comes to
indexing I am concerned about the the extent to which there
might end up being different indexing strategies. At one
point there was discussion between the itemis Xtext folks
and the SAP Query2 folks, but that never went anywhere and
the Query2 guys went AWOL. Certainly Xtext relies heavily
on indexing and has mature technology that performs well...
[PGa] The view relies exclusively on the
ECrossReferencerAdapter for indexing.
- Sphinx, as it can be considered as a basic UI
component for building modelling workbenchs
Sphinx would appear to be
quite a nature fit. I'm not sure the extent to which Sphinx
is decomposed into well modularized small features that
allow individual capabilities to be used without pulling in
too many things that might not be used...
- Other modelling infrastructure projects like
EEF or Amalgam
So is it primary a UI thing
or is there underlying searching/indexing technology
involved as well?
[PGa]
Definitely UI.
What do you think about it?
That depends on the details.
Of course I'm generally reluctant to take on yet more
support burden for a component that's ubiquitously taken for
granted...
Pierre GAUFILLET
Software Engineering Specialist
Avionics and Simulation Products Software -
EYYW
AIRBUS
Mailto: pierre.gaufillet@xxxxxxxxxx
Polarsys Industrial Working Group: http://www.polarsys.org
TOPCASED: http://www.topcased.org
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc