Operationalizing the Integration of User Interaction Specifications in Modeling Editor Synthesis
summary
Claims that interaction behavior must be specified alongside abstract and concrete syntax and concretely anchors those semantics in a Statecharts controller; implements a pipeline of interface, interaction and deployment languages that compiles to executable editors (web and Arduino) and reproduces Eclipse/Sirius behaviors for Game of Life and a MIDI-mapped music sheet. Core engine is a RETE-based refinement that incrementally generates states and transitions; measured 300 rules <3s for Rete construction, manual models use 4–60 rules and refinement time grows roughly quadratically. Works but demands large rule sets, a ready API library, and targets graphical DSMs.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:06Modeling editor limits
- 2:54Domain-specific interaction modeling
- 6:31Refining interaction rules
- 15:05Code generation and deployment
- 16:13Generated editors demo
- 18:01Evaluation and scalability
- 20:56Limitations and future work
- 22:25User studies and experiments
- 23:37Current implementation
- 24:31Q&A
related talks
40mAn Interdisciplinary View on Prototypes - Towards Executable Models That Can Be...
21mAconite: Towards Generating Sirius-Based Graphical Editors from Annotated Metamodels
28mManipulating GUI Structures Declaratively
01h 32mResearch Methods for Designing Next-Generation Programming Systems
14mAutomating the Synthesis of Recommender Systems for Modelling Languages
35mThe holy war of modeling notations - what fits best and why?
28mWhat You See Is What It Does: A Structural Pattern for Legible Software
52mThink Abstractly, Work Concretely