Open Issues
Proxima
Enriched Document
Incrementality
Open/Save document
When a document contains parse errors, it is not entirely clear how to save it, since the parseErr node contains the presentation that failed to parse. Perhaps the XML format needs to support a representation for (parseable) presentations as well.
Currently, extra state is not stored in the XML representation. For the Helium editor, this means that whitespace is not saved. A solution would be to include presentation id's in the XML, and store the whitespace list as some kind of meta data. Perhaps something similar needs to be done for extra state in the enriched document.
HACK: The enriched document has an extra Document parameter, which is required for the generated popup menus for structure editing.
Graphs
Vertices have an id, which is used to specify edges. Should this id be unique?
If so, we cannot use id's to model equal vertices in different graphs, so document vertices must contain an extra id for each vertex.
Creation of a new vertex on document level must create an id for the vertex. We could rely on the parser to do this, but then after each document edit, a parse present cycle must be performed.
--
MartijnSchrage - 24 Feb 2010
