3906

Yet another attempt at decomposing incremental edits in some clean way.
The new idea now is that I need to only modify the screen using a
restricted vocabulary of actions:
  render-all
  render-recipe-side
  render-sandbox-side
  render-recipe-errors
  render-line-from-cursor
  render-line-from-start
  erase-line-from-cursor
  render-character-at-cursor
  erase-character-at-cursor

However, decomposing insert-at-cursor is challenging; how to manipulate
cursor-row and cursor-column without also pretending to print to screen?
Do I need to decompose `editor` into multiple containers so that I can
keep cursor-row and cursor-column with screen modifications? Here's what
`editor` looks like after all layers:

  container editor [
    data:&:duplex-list:char
    top-of-screen:&:duplex-list:char
    bottom-of-screen:&:duplex-list:char
    before-cursor:&:duplex-list:char
    left:num
    right:num
    bottom:num
    cursor-row:num
    cursor-column:num
    indent?:bool
    undo:&:list:&:operation
    redo:&:list:&:operation
  ]

It's not obvious that there's a clean way to split all these fields.

1 files changed, 13 insertions, 0 deletions

diff --git a/030container.cc b/030container.cc
index 2e5da42e..507dace3 100644
--- a/030container.cc
+++ b/030container.cc
@@ -900,3 +900,16 @@ void check_invalid_types(const type_tree* type, const string& location_for_error
       raise << location_for_error_messages << "unknown type in " << name_for_error_messages << '\n' << end();
   }
 }
+
+string to_original_string(const type_ordinal t) {
+  ostringstream out;
+  if (!contains_key(Type, t)) return out.str();
+  const type_info& info = get(Type, t);
+  if (info.kind == PRIMITIVE) return out.str();
+  out << (info.kind == CONTAINER ? "container" : "exclusive-container") << " " << info.name << " [\n";
+  for (int i = 0;  i < SIZE(info.elements);  ++i) {
+    out << "  " << info.elements.at(i).original_string << "\n";
+  }
+  out << "]\n";
+  return out.str();
+}