Key simulation

[rksm]

This implements a simple form of triggering commands and insertions by simulating keys. Like:

var keys = require('ace/lib/keys');
// one key combo at a time
keys.simulateKey(editor, 'Shift-Right');
keys.simulateKey(editor, 'Command-Shift-d');
keys.simulateKey(editor, 'Control-a');
// or multiple
keys.simulateKeys(editor, 'H e l o Left l Command-Shift-Left');
/*...*/

todo:

• support series of keys (like keys.simulateKeys(editor, 'Right Right Command-Down'))
• base keys.send / old vim sendKeys code upon simulateKeys

[rksm]

Is there something wrong with this PR? Except for the main functionality of key simulation it is attempt to make the key handling a bit more uniform.

[nightwing]

I think hashId can't be -1, it's equal to 0 | (e.metaKey ? 1 : 0) | (e.altKey ? 2 : 0) | (e.shiftKey ? 4 : 0) | (e.ctrlKey ? 8 : 0);

[nightwing]

Sorry for the delay with reviewing this. The changes generally look good, but i don't like that this adds code needed only for testing into the main module.

[nightwing]

@rksm Did you need simulateKeys in editor itself or only in tests? I want to move it and it's helpers into separate module.

[rksm]

I need it as a feature outside of tests but whether it resides in a separate module or not doesn't matter.

[knod]

Has the ability to simulate key presses been added in some fashion? Not just content keys, but modifier keys as well and the tab key functionality.

To take tab as an example - just inserting a tab works for most occasions, and indenting might be handled as described here: http://stackoverflow.com/questions/24607730/ace-editor-javascript-triggering-a-tab-press-event-for-ace-editors-event-hand/24608974#24608974. Unfortunately, more uses of tab keep popping up. With snippetManager, pressing tab navigates to the next specified text in a snippet and I want that functionality as well.

I don't want to have to recreate all the functionality for each plugin I use. I'd like to just simulate an actual key being pressed or held. Is this possible?

[rksm]

@knod Since this feature seems to be unwanted I ended up publishing it in an extension. ace.ext.keys.simulateKeys() works with modifiers and key sequences. I understand @nightwing concerns to not add "test code" but for the use in Lively we use this feature in production as well (to integrate ace and non-ace keyboard handlers).

[rksm]

@knod ace.improved has some doc now, https://github.com/rksm/ace.improved#aceextkeys

[knod]

@rksm Thanks, I'll look into that. I have a lot else to work on, but this will become a major issue soon, so I'm glad to see there's a way to handle it out there.