summaryrefslogtreecommitdiff
path: root/viz/src/plan.org
diff options
context:
space:
mode:
authorJSDurand <mmemmew@gmail.com>2023-06-02 14:51:25 +0800
committerJSDurand <mmemmew@gmail.com>2023-06-02 14:51:25 +0800
commit1455da10f943e2aa1bdf26fb2697dafccc61e073 (patch)
tree7d6c51a1040fc6b05bf3a19386e05016f8c0ab0f /viz/src/plan.org
parent83c66eb77c6affaa9ac4fabd808556613c5bf973 (diff)
viz: finished decycle algorithm
Diffstat (limited to 'viz/src/plan.org')
-rw-r--r--viz/src/plan.org27
1 files changed, 27 insertions, 0 deletions
diff --git a/viz/src/plan.org b/viz/src/plan.org
new file mode 100644
index 0000000..dd7c9ab
--- /dev/null
+++ b/viz/src/plan.org
@@ -0,0 +1,27 @@
+#+TITLE: Plan of the package
+#+AUTHOR: Durand
+#+DATE: <2023-05-07 Dim 00:03>
+
+* Things to do [0/4]
+
+- [ ] Design an incremental format to encode forests [0/3]
+ + [ ] The format consists of a sequence of "actions". Each action
+ modifies the graph as a unit. For example, adding a vertex and
+ edges are actions, and cloning a node can be an action as well.
+ + [ ] The format has two functions that specific readers / writers
+ should implement. For example, the forests for the chain-rule
+ machine can implement the two functions. In the trait, the
+ implementer can choose which actions are availabel, and how each
+ action modifies the graph.
+ + [ ] Maybe each stored file can choose to include the final graph,
+ so that the displayer has the option to display only the final
+ graph without going through all modifications just to produce the
+ final graph.
+- [ ] Implement serialization
+- [ ] Implement de-serialization
+- [ ] Implement display of graphs
+ + [ ] Implement a graph display "server" that determines the
+ coordinates to be drawn on the canvas.
+ + [ ] Implement a graph display client, perhaps in Emacs, that
+ actually executes the display instructions.
+