2013
DOI: 10.1007/978-3-642-38883-5_11
|View full text |Cite
|
Sign up to set email alerts
|

Robust Real-Time Synchronization between Textual and Graphical Editors

Abstract: Abstract. In modern Integrated Development Environments (IDEs), textual editors are interactive and can handle intermediate, incomplete, or otherwise erroneous texts while still providing editor services such as syntax highlighting, error marking, outline views, and hover help. In this paper, we present an approach for the robust synchronization of interactive textual and graphical editors. The approach recovers from errors during parsing and text-to-model synchronization, preserves textual and graphical layou… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
12
0

Year Published

2013
2013
2018
2018

Publication Types

Select...
5
1

Relationship

2
4

Authors

Journals

citations
Cited by 14 publications
(12 citation statements)
references
References 19 publications
0
12
0
Order By: Relevance
“…This works because all notational styles are implemented using the same projectional architecture. In contrast, maintaining an integrated overall model created with editors that combine parsing and diagram editing is challenging for a number of technical reasons [28]. These include that parser-based editors use (qualified) names to represent program node identity, whereas graphical editors natively use IDs for this purpose or that references in ParEs are created via name binding, and graphical editors use the unique ID.…”
Section: Efficiently Entering (Textual) Codementioning
confidence: 99%
“…This works because all notational styles are implemented using the same projectional architecture. In contrast, maintaining an integrated overall model created with editors that combine parsing and diagram editing is challenging for a number of technical reasons [28]. These include that parser-based editors use (qualified) names to represent program node identity, whereas graphical editors natively use IDs for this purpose or that references in ParEs are created via name binding, and graphical editors use the unique ID.…”
Section: Efficiently Entering (Textual) Codementioning
confidence: 99%
“…Challenge 1. Past Spoofax work [21] to generate meta-models from grammars suffers from the same limitations as Xtext (above). However, Stratego/XT [22] can be used within Spoofax to address this challenge.…”
Section: Spoofaxmentioning
confidence: 99%
“…Although it was not originally intended to create models, there is work [21] showing that Spoofax can be used for this purpose. We now relate the challenges from Sect.…”
Section: Spoofaxmentioning
confidence: 99%
“…Finally, there seems to be a convergence towards language workbenches where multiple, heterogeneous notations or editing modes co-exist within one language: MPS already supports graphical, tabular, symbolic, and textual notations; Spoofax is currently working towards integrating graphical notations (see e.g., [56]); and in the Onion language workbench, textual parsing is combined with projectional editing. Language reuse and composition.…”
Section: Observationsmentioning
confidence: 99%