| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
|
|
|
|
testing
|
|
|
|
according to my yet unwritten coding conventions:
1. no single line blocks
2. no empty lines without a good reason
|
|
deleted
|
|
|
|
1. move the sugg variable to textanalysis.js instead of the ui part
2. use a callback for the autocomplete widget (it supports three
options: array, string as url for a json returning service, or callback)
3. use a dictionary instead of an array to keep the list of suggestions.
We iterate on the dictionary instead of using a Trie or some other
datastructure in the callback. But the dictionary avoids iteration when
adding a word. Overall a loss in performance, but not noticeable.
Googling / memory suggests a Trie is what we want here, but I'm
postponing that for later. See:
http://ejohn.org/blog/javascript-trie-performance-analysis
|
|
|
|
|
|
Fixes #58
|
|
|
|
|
|
|
