• Ensure that state names are saved and restored by the commands subsystem
• Allow renaming to be undone and redone
• Move the cursor to the end of the name setting input when it is opened

• Added a map to the States struct to store state names
• Added default name generation like JFLAP (q1, q2...)
• Added egui context menu button and window for renaming states
• Save and load names from JFF files

• Added logic to use Window.showSaveFilePicker() if it is available
  • This is much better than the dialogless save, but is only available on some platforms (luckily including Chrome)
  • This should eventually be used for the "Save as..." feature
    • How can this distinction be reconciled when the dialog isn't available?
• Added simple implementation for creating a new file

• Added implementation for DocumentCommand::SaveJFF
  • Serializes fa and states to an XML tree
  • Then sends a string with its contents to the frontend
• Added a Save button to the File menu
• Added code utilizing FileSaver to save the file
  • This currently only supports saving to a single file named sugarcubes.jff

Most exciting PR so far!!

• Added xmltree dependency for easily parsing XML to a tree of enums
• Cleaned up message handling by moving top message handling to a new struct
• Added a static buffer of DocumentCommand, that can be written to by JS
• Implemented reading a JFF automaton structure from JFLAP
  • Reads all states and adds them to a new States + FiniteAutomaton pair, and then reads all the transitions and adds them to the FiniteAutomaton
  • If the entire reading occurs without error, the real fa and states are overwritten

• Added Clear and Load from file buttons to the multiple run panel
• Added functionality for reading files line-by-line and loading them to the multiple run panel
• Made the body of the multiple run panel into a scrolling area
• Disabled resizing of the multiple run panel
  • In the future, resizing should definitely be enabled
  • Sizing below the default is currently very finicky in egui

In the future, more checks should be done on the file, likely all on the backend. It should probably reject certain file extensions. Perhaps, it should only accept certain file extensions, including .txt and files without an extension. Base this on what JFLAP does.

• Created a miniquad plugin to expose JS function to Rust, using sapp-jsutils
• Implemented file loading function on frontend
• Added proof-of-concept file loading
  • Appends the file name to the multiple-run list
• Moved the top panel into a single-threaded static

• Pressing Enter on the last line of the multiple run list will add a new line, provided that the last line is not empty
• If the last line of the multiple run list is empty, it will not be tested when Run is clicked

• Added a new simulation mode, allowing multiple strings to be evaluated instantly
• Fixed a bug with detecting accepts and rejects involving lambda transitions
• Adjusted camera position to automatically account for horizontal components

The major TODO is to allow the user to add rows to the multiple run area.

• Added a "Fast Run" button to the simulate menu
• Began refactoring top panel code to be split up
• Added an early implementation of fast running
  • This requires a hard iteration limit for safety, but should eventually involve a utility struct that facilitates user confirmation

• Consolidated almost all top panel features to commands
  • Added a TopPanelCommand enum that can wrap a Command, or things like Undo, Redo, Step, etc.
• Added commands for creating states and transitions
  • So they can now be Undone
  • This involves generating the state ID before adding it, which in theory makes it non-atomic, so be careful

These features make me mostly satisfied with the set of undoable actions. I now think it is optional to 1) implement Undo/Redo for moving states, and 2) edit transitions in the context menu. Therefore, I moved them to an "under consideration" section in the README. That said, I think features like large-scale alignment of states should be undoable.