| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
zoom in/out; clicks on nodes/edges
|
|
introduces two new modules:
scripts/consts.js
scripts/signal.js
signal is a thin wrapper for jquery('window').on and
jquery('window').trigger, which seems like an adaquete signal library -
there are faster things around, but why introduce another dependency.
|
|
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.
|
|
|
|
|
|
|
|
no atomicity - nodes/links recorded as separate additions
We record both temp (state == 'temp') and not temp nodes,
can be filtered during analysis.
|
