rhizi - Connective intelligence

summary refs log tree commit diff

path: root/scripts/textanalysis.ui.js

Age	Commit message (Collapse)	Author
2014-11-11	textanalysis.ui:	LV-426
	- clean module header - nod dep change - rename RZ -> rz_core - use non-named module definition
2014-11-11	textanalysis: reduce API	Alon Levy
	textanalysis exposes the current selected type plus functions to increment or decrement it, hides the typeindex and nodetypes.
2014-11-10	graph/textanalysis.ui: lastnode is now the last added node (fixes #124)	Alon Levy

2014-11-10	rename rhizicore -> rz_core, move towards common rz_ prefix	LV-426

2014-11-09	default not to commit changes to backend	LV-426

2014-11-09	commit diff_set upon sentence analysis:	LV-426
	- backend_commit - allows client accumulating changes & select better commit timing
2014-11-09	code standard: use a single var at start of functions (just one big case) ↵	Alon Levy
	and some whitespace
2014-11-09	s/textAnalyser2/textAnalyser/	Alon Levy

2014-11-03	Fixes #121 - Large part of map unclickable due to autocomplete suggestions	Alon Levy
	See http://stackoverflow.com/questions/5643767/jquery-ui-autocomplete-width-not-set-correctly/11845718#11845718 A relevant bug on jquery-ui for width: http://bugs.jqueryui.com/ticket/7303 Additionally I considered measuring the exact width before noticing I can set the width to 10px and the text itself is perfectly clickable, see: http://stackoverflow.com/questions/6961022/measure-bounding-box-of-text-node-in-javascript
2014-10-28	textanalysis.ui: use input event if it exists, fallback to polling of 50ms ↵	Alon Levy
	(not 5ms) otherwise
2014-10-28	textanalysis{,.ui}: fix remaining globals, use strict	Alon Levy

2014-10-26	history switch to events; using a single GRAPH_DIFF action. todo - replay; ↵	Alon Levy
	zoom in/out; clicks on nodes/edges
2014-10-24	textanalysis.ui: shift-tab now changes type back, tab forward	Alon Levy

2014-10-24	fixes #106	Alon Levy
	broken by define addition (require.js)
2014-10-21	fix test_analyzer after require.js	Alon Levy

2014-10-20	introduce require.js and rewrite tests	Alon Levy
	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.