| Age | Commit message (Collapse) | Author |
|
|
|
need better graph accessors to give only the 'real' nodes & links - that will fix some of the tests, leaving the real wrong ones
|
|
|
|
|
|
|
|
Yes, I'm being lazy. The purpose of require.js is to allow writing
modules, i.e. individual smaller then the whole files with clear
dependencies. This is achieved by using a new api provided by
require.js:
define, require, requirejs
Read more at [requirejs] (http://requirejs.org)
Tests have been rewritten to work correctly with require.js; they still
use jsdom.
Test output is now stored in the repository, all tests are run via
run_tests.js; This is a hack - once a good harness (with assertions,
suites - unittest like) presents itself it will be used.
Hidden here is also using FileSaver for history saving, so history is
saved to history.json instead to a random name. Plus dropping some dead
code.
|
|
|
|
|
|
|
|
|
|
Actually seems that the proper way to save nowadays is the [download]
(https://html.spec.whatwg.org/multipage/semantics.html#attr-hyperlink-download)
attribute of a 'a' element, but that's also supported by the added
[FileSaver.js] (external/scripts/FileSaver.js)
|
|
|
|
|
|
#91 Fixed
|
|
It’s fixed except when nodes have “….” in it. That’s issue #79 which I
still haven’t figured out.
|
|
The whole lower case thing is a hack. We should separete id and name.
But right now it seems to be holding.
|
|
|
|
textanalysis, firefox sometimes lags
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Not required right now, triggered by reverted patch.
|
|
This reverts commit e58e0c0b520d4abb971d3917712340330e5d85ff.
It actually destroyed quite a lot of things, specifically even a simple
sentence ended up being a chainlink. I need to rethink the
'abnormalGraph' predicate.
|
|
|
|
Fixes #86
Well, almost - the center node contains the 'a and b and c' (with extra spaces too).
node test_analyzer.js '#a and #b and #c are cool'
digraph {
BUBBLE;
a;
b;
c;
"new node";
"a and b and c are cool";
a -> "a and b and c are cool";
b -> "a and b and c are cool";
c -> "a and b and c are cool";
}
|
|
node test_analyzer.js '#a and #b and #c are cool' | dot -Tpng > /tmp/temp.png; xdg-open /tmp/temp.png
Todo: use stdin, then it will be a total pipe
Todo: make this a rhizi debug feature that displays the image in the
browser?
|
|
|
|
This is more of #49 basically, just for a more complex sentence.
I've kept the flow that we have, but augmented the graph change check
(myGraph.compareSubset) and introduced some helper functions for sets on
the way.
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #49
Note about solution: in general we need to find out whether the graph
from the new text (NewVertices, NewLinks) is homologous to the graph
from the old text (OldVertices, OldLinks). The implemented solution only
checks an easier case, where there is a single renamed vertex.
A better solution to do later:
- have textanalysis have state
- have textanalysis return the difference from the last state:
nodes added
nodes deleted
nodes changed
- plus for bonus refactor all the editing functions (edit* in myGraph)
|
|
event handler
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
changing state of existing node results in ability to delete nodes while
creating a new sentence by inputting a node name and then deleting it.
This was fixed for the common case in a previous commit, but not for the
case of loading from storage.
|
|
|