Open cashaffer opened 10 years ago
The changes that you made have stopped the concept map window from displaying. There is what appears to be an error message in the console, but it flies by too fast when I click the link and the page changes to the glossary.
Turns out the issue with no concept map displayed comes from changes in the update to how it handles data in localStorage, combined with old data in localStorage.
With the changes, the issue of "edge labels" is fixed, and the backup works in principle. But here is a new round of issues:
If I click on "graph" then on "edges" it says that "the term edges is not in the glossary". This also happens if I click on the term "edges" in the glossary (instead of in the concept map). I think the issue here relates to the display anchor text vs. the actual term. "edge" is the glossary term, while "edges" is the display label. Note that I went back and recompiled the book with the :to term: directive for "graph" to read:
:to-term: edges
So it has the information to know (even in the concept map) that the glossary term should be "edge". This compiles correctly, and displays "edges" as the node text, but does not behave correctly on the click.
I am getting feedback that we need greater visual contrast between the "term" nodes and the "label" nodes. I think that it might work to remove the white background and edge shading around the "label" nodes. In this way, the will look more like labels and less like nodes.
1) It should be possible to back up to the last state before the current click. 2) We need more context for "leaf" nodes. Currently, when you click on a "leaf" node, you get a map with just a single node on it (and nowhere to go). 3) There are actually two types of nodes in the concept map graph. There are the terms, and there are the labels for the edge. For example, from "graph" there is a link to "contains" (which is an edge label, not a term), with links to "vertices" and "edges" (which are terms). Nothing should happen when one clicks on an "edge label" node. Right now it thinks this is a term that is not in the glossary. 4) We need to make a distinction between the display text in a term node and the actual term as it appears in the glossary. For example, I want "edges" to appear as a label in the concept map, but the actual term is "edge". This will require some sort of change to the :to-term: directive. 5) The graph layout is still problematic. For example, see the graph that results from clicking on "graph". There are a lot of overlapping nodes. I also notice that there is some randomness involved. If I repeatedly click on "graph" in the glossary, the resulting concept map layout changes each time.