![]() ![]() ![]() In order to facilitate using the mouse to position the cursor and make selections we'll want someway to link nodes in the DOM with nodes in the parse tree. I think the biggest challenge will be generating new nodes in the format expected by buildTree. The parse tree doesn't support anyway to navigate to sibling nodes or to navigate to a parent node, but it could be made to do so. If we go with the parse tree approach we'd want to be able to navigate through the tree. ![]() make a selection of multiple characters and render itĪll of this seems incredible difficult to do if we try to map back to the original input string.render a cursor at the correct location.move a cursor around via the keyboard and mouse.There are various things that an editor needs to be able to do: Editing the parse tree is complicated by the fact that we haven't stabilized the parse tree yet. In the case of editing the LaTeX string, determining which characters from the original source should be updated when the user makes an edit can be tricky especially when macros are involved. There are a couple of approaches to implementing an editor:īoth have their challenges. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |