52fe892bae
invert logical relationship with flag
...
otherwise updates don't actually propogate
9 years ago
938df2b92f
lock the editor until the chain has synced
...
add 'onAbort' hook. lock the editor if the connection fails.
9 years ago
e5bef52850
reintroduce the toolbar
9 years ago
c246adc57b
Lock contenteditable until chain is done syncing.
...
Don't bother patching the dom until the chain has synced
9 years ago
1c0074258c
go back to using diffDOM from bower
...
The latest version is required. You'll need to update.
9 years ago
79bd82a62e
main.js : integrate with patched diffDOM
9 years ago
7e367e770e
resize vdom debug panel to 30% width
9 years ago
e87a4599a4
main.js : tiny patch until things are working correctly.
9 years ago
9ce59c985f
only do stuff with the cursor when a remote edit takes place
9 years ago
7e7f1fee76
include abstracted json-ot, add comments, start to use cursor stuff
9 years ago
fbb9163e42
main.js : clean up and commit before making big-ish changes for cursor fixing
9 years ago
3cb94b8d80
jshint compliance
9 years ago
4a05a859e6
fix initialization routines
9 years ago
967d636df9
address more jshint complaints
9 years ago
a7da21ccba
Remove the cursor treatment
9 years ago
86c4a69a97
Switch to patching with DiffDOM for testing :D
9 years ago
37db31b09e
Attempt an operational transformation and if the result is not valid JSON then fail
9 years ago
e16299b5c4
Revert "restub OT until it's verified"
...
This reverts commit 350c9e6c76
9 years ago
350c9e6c76
restub OT until it's verified
9 years ago
9b13fd8f34
pull cursor correction code out of main.js
...
put it in cursor.js
9 years ago
b43674eb53
switch back to two-panel layout
9 years ago
aa3880f442
up to date
9 years ago
d96124229b
clean up realtime-input.js, break API
...
use an object for configuration, so as to be more extensible.
modify applications which use the API to match.
9 years ago
e220113e98
fix the 'crapstorm' bug
9 years ago
08fb010627
give 'onChange' a name
9 years ago
d14e42fedd
start on a vdom-based wysiwyg realtime
...
There are still a few conditions that cause it to 'explode'
when different browsers disagree on element semantics.
Overall it's a much cleaner approach, but it will require
extensive tuning to improve performance, as there are still
many complete dom traversals which will not scale for large documents
9 years ago
ansuz