eclipse-gemoc / eclipse-gemoc/gemoc-studio-modeldebugging

Two .dsl editors in the GEMOC Studio

Open
#174 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
6
Forks
14
PR merge metrics
No merged PRs in 30d

Description

There are currently 2 .dsl editors in the GEMOC Studio
one provided by GEMOC that also provides completion, highlighting, navigation and advanced checking (metaprog) (cf. https://github.com/eclipse/gemoc-studio-modeldebugging/blob/master/commons/plugins/org.eclipse.gemoc.dsl.ui/plugin.xml) and one provided by ALE (cf. https://github.com/gemoc/ale-lang/blob/master/plugins/org.eclipse.emf.ecoretools.ale.ide.ui/plugin.xml)

The one provided by ALE is basic as it simply opens the file as a java property file. This is fine if ALE is installed by itself without GEMOC but leads to ambiguity about which editor is the most efficient when used in the GEMOC Studio.

I suggest improving the name of both editors in order make sure which one is used

Contributor guide

No contributing guide indexed for this repository

Research direction

Compare the editor declarations in commons/plugins/org.eclipse.gemoc.dsl.ui/plugin.xml and plugins/org.eclipse.emf.ecoretools.ale.ide.ui/plugin.xml. Identify the two .dsl editor labels and update them so users can distinguish the GEMOC editor from the ALE editor, then verify both declarations remain valid.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.