Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

re-introduce Ecore registration UI and autoregister nature #14

Closed
dvojtise opened this issue Oct 16, 2017 · 10 comments
Closed

re-introduce Ecore registration UI and autoregister nature #14

dvojtise opened this issue Oct 16, 2017 · 10 comments

Comments

@dvojtise
Copy link
Contributor

Before switching to eclipse, the GEMOC studio was using diverse commons libraries. (https://github.com/diverse-project/tools/tree/master/commons-eclipse/org.eclipse.emf.ecoretools.registration.ui)
These libraries contains 2 useful features :

  • register ecore (popup menu + view)
  • a builder nature that allows to automatically register all ecore files present in the project.

these features were not copied directly to gemoc commons because it is partly redundant with code in ecoretools (https://github.com/eclipse/ecoretools/tree/master/org.eclipse.emf.ecoretools.registration)
Ecoretools actually contains an early version of diverse commons code (that I have developed several years ago)
It would be interesting to contribute the newest version directly into ecoretools.

@dvojtise
Copy link
Contributor Author

This feature is really useful when working with concurrency tooling (ocl/moccml editor works better with it)

@ebousse
Copy link
Contributor

ebousse commented Jun 21, 2018

Not sure to clearly understand the situation. Do we simply need to add ecoretools.registration to the GEMOC Studio, or is there more to do?

@dvojtise
Copy link
Contributor Author

Yes, more or less, the proper way would be to contribute to ecoretools projet itself, but my experience to submit there prove to be a long process even for tiny PR. In the meantime, a copy of what we had in the past would do the job until we properly push it in ecoretools project

@dvojtise
Copy link
Contributor Author

Another point to be aware before contributing or adding a copy in our repos is that an early version of the api part of the ecore registration is supposed to be already in ecoretools project see https://github.com/eclipse/ecoretools/tree/master/org.eclipse.emf.ecoretools.registration

but it doesn't seem to be installed in the studio 😞

This early version doesn't has the autoregister builder, but only the manual register action.

@dvojtise
Copy link
Contributor Author

Mhmm this component is actually compiled by ecoretools but not included in any feature and then not available in the their update site : http://download.eclipse.org/ecoretools/updates/releases/3.2.0/neon/plugins/?d

@dvojtise
Copy link
Contributor Author

question opened on ecoretools forums: https://www.eclipse.org/forums/index.php/t/1093853/

@dvojtise
Copy link
Contributor Author

@dvojtise dvojtise self-assigned this Jul 16, 2018
@dvojtise
Copy link
Contributor Author

Bug opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=537295 with corresponding gerrit queries implementing it.

Now waiting for review from EcoreTools project commiters

@dvojtise
Copy link
Contributor Author

when this feature will be there, we can also change the text in http://download.eclipse.org/gemoc/docs/nightly/K3FSM-example.html#_add_textual_editor

and instead of replacing the import (from nsUri to platform schema ) in order to use xtext smoothly, we can simply add the autoregister nature to the project containing the ecore

dvojtise added a commit that referenced this issue Aug 22, 2018
we currently need to manually replace the nsUri by a platform uri in
xtext file because the ecore nsuri in not known in the current workspace

Signed-off-by: Didier Vojtisek <didier.vojtisek@inria.fr>
dvojtise added a commit that referenced this issue Aug 24, 2018
…odeling) (#104)

New system test suite based on official example K3FSM (language and modeling)

* new Language WB test suite based on k3fsm
* new test DeployOfficialExampleK3FSM_Test
* introducing test for the modeling workbench
use a pomless tycho configuration to build required languages to be
added in the target platform

* tests about running the K3FSM language on the official example models
* new test (currently ignored) about the end of the execution
see eclipse-gemoc/gemoc-studio-modeldebugging#66

* add dsl file in build.properties
temporary workaround for
eclipse-gemoc/gemoc-studio-modeldebugging#65

* workaround for #14
we currently need to manually replace the nsUri by a platform uri in
xtext file because the ecore nsuri in not known in the current workspace

* new docker environment to help developer launching full build
* add gtk3 to docker image
* added a way to launch only system tests in the docker


Signed-off-by: Didier Vojtisek <didier.vojtisek@inria.fr>
dvojtise added a commit to gemoc/gemoc-studio-eclipsefork that referenced this issue Nov 5, 2018
…odeling) (eclipse-gemoc#104)

New system test suite based on official example K3FSM (language and modeling)

* new Language WB test suite based on k3fsm
* new test DeployOfficialExampleK3FSM_Test
* introducing test for the modeling workbench
use a pomless tycho configuration to build required languages to be
added in the target platform

* tests about running the K3FSM language on the official example models
* new test (currently ignored) about the end of the execution
see eclipse-gemoc/gemoc-studio-modeldebugging#66

* add dsl file in build.properties
temporary workaround for
eclipse-gemoc/gemoc-studio-modeldebugging#65

* workaround for eclipse-gemoc#14
we currently need to manually replace the nsUri by a platform uri in
xtext file because the ecore nsuri in not known in the current workspace

* new docker environment to help developer launching full build
* add gtk3 to docker image
* added a way to launch only system tests in the docker


Signed-off-by: Didier Vojtisek <didier.vojtisek@inria.fr>
@dvojtise
Copy link
Contributor Author

done and included in PR #118

dvojtise added a commit to eclipse-gemoc/gemoc-studio-modeldebugging that referenced this issue Jan 15, 2020
…odeling) (#104)

New system test suite based on official example K3FSM (language and modeling)

* new Language WB test suite based on k3fsm
* new test DeployOfficialExampleK3FSM_Test
* introducing test for the modeling workbench
use a pomless tycho configuration to build required languages to be
added in the target platform

* tests about running the K3FSM language on the official example models
* new test (currently ignored) about the end of the execution
see #66

* add dsl file in build.properties
temporary workaround for
#65

* workaround for eclipse-gemoc/gemoc-studio#14
we currently need to manually replace the nsUri by a platform uri in
xtext file because the ecore nsuri in not known in the current workspace

* new docker environment to help developer launching full build
* add gtk3 to docker image
* added a way to launch only system tests in the docker


Signed-off-by: Didier Vojtisek <didier.vojtisek@inria.fr>
dvojtise added a commit to eclipse-gemoc/gemoc-studio-modeldebugging that referenced this issue Jan 15, 2020
…odeling) (eclipse-gemoc/gemoc-studio#104)

New system test suite based on official example K3FSM (language and modeling)

* new Language WB test suite based on k3fsm
* new test DeployOfficialExampleK3FSM_Test
* introducing test for the modeling workbench
use a pomless tycho configuration to build required languages to be
added in the target platform

* tests about running the K3FSM language on the official example models
* new test (currently ignored) about the end of the execution
see #66

* add dsl file in build.properties
temporary workaround for
#65

* workaround for eclipse-gemoc/gemoc-studio#14
we currently need to manually replace the nsUri by a platform uri in
xtext file because the ecore nsuri in not known in the current workspace

* new docker environment to help developer launching full build
* add gtk3 to docker image
* added a way to launch only system tests in the docker


Signed-off-by: Didier Vojtisek <didier.vojtisek@inria.fr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants