- 28 Jun, 2011 1 commit
-
-
Joel Martin authored
Issue https://github.com/kanaka/noVNC/issues/69 Thanks https://github.com/EdSchouten for the catch. Import from websockify 9a2b50d8.
-
- 26 Jun, 2011 5 commits
-
-
Joel Martin authored
-
Joel Martin authored
Just have a list here without all the links.
-
Joel Martin authored
Pull websockify 7f487fdbd. The reocrd parameter will turn on recording of all messages sent to and from the client. The record parameter is a file prefix. The full file-name will be the prefix with an extension '.HANDLER_ID' based on the handler ID.
-
Joel Martin authored
- Update test mode calls to work with separate websock module. - Pull in include/websock.js update 7f487fdbd from websockify.
-
Anthony Young authored
-
- 13 Jun, 2011 3 commits
-
-
Joel Martin authored
-
Joel Martin authored
-
Joel Martin authored
Broadway uses noVNC keyboard/input handling. Link to it.
-
- 19 May, 2011 2 commits
-
-
Joel Martin authored
Fixed minor typo in util/launch.sh informational output (s/to to/to/)
-
Sam Mussmann authored
s/to to/to/
-
- 12 May, 2011 2 commits
-
-
Joel Martin authored
-
Joel Martin authored
Including HyBi-07 support and refactor of send/recv.
-
- 11 May, 2011 2 commits
-
-
Joel Martin authored
- Add conf_defaults which accepts an array of configuration attributes. - Split out user configuration defaults from the actual configuration object. - Add mode field and enforce read-only, write-once, read-write modes.
-
Joel Martin authored
API changes: - include/canvas.js renamed to include/display.js - Display.rescale() method removed from API. Use Display.set_scale() instead. - Make logo configuration attribute of Display and display it when clear() is called if it is set. API deprecations: - use RFB onUpdateState instead of updateState. - use RFB onClipboard instead of clipboardReceive. See https://github.com/kanaka/noVNC/wiki/ModuleAPI for detailed noVNC modules and API description. Expand and normalize the event/callback interfaces. Standize on "onEventName" form for callbacks. Callback Renames: - RFB updateState -> onUpdateState - RFB clipboardReceive -> onClipboard - Keyboard keyPress -> onKeyPress - Mouse mouseButton -> onMouseButton - Mouse mouseMove -> onMouseMove Callback Additions: - RFB onPasswordRequired - RFB onBell - RFB onFBUReceive - RFB onFBUComplete Other: - Add array type support to Util.conf_default() - Removed a bunch of routines from the Display API that were just used internally and not actually by noVNC: flush, setFillColor, imageDataGet, imageDataCreate, rgbxImageData, rgbxImageFill, cmapImageData, cmapImageFill. - More keyboard/mouse logging when debug turned on. - Some JSLinting
-
- 09 May, 2011 2 commits
-
-
Joel Martin authored
-
Joel Martin authored
Pull from websockify a339a4856.
-
- 29 Apr, 2011 2 commits
-
-
Joel Martin authored
-
Joel Martin authored
Still buggy so not yet activated in the UI, but the hooks are at least here.
-
- 24 Apr, 2011 3 commits
-
-
Joel Martin authored
Separate the links from each other so it's obvious where the links are.
-
Joel Martin authored
-
Joel Martin authored
github changed something about relative links.
-
- 21 Apr, 2011 1 commit
-
-
Joel Martin authored
-
- 19 Apr, 2011 1 commit
-
-
Joel Martin authored
Derived classes will almost certainly want to make use of the raw info.
-
- 15 Apr, 2011 2 commits
-
-
Joel Martin authored
Issue #21 - non-US key handling.
-
Joel Martin authored
Issue #21 - non-US keyboard layouts. The code section for tab, backspace and enter was commented out for testing but got checked in that way. Fix that.
-
- 14 Apr, 2011 1 commit
-
-
Joel Martin authored
Requested by Alexander Larsson at Red Hat to allow incorporation of solution into HTML5 gtk 3.0 backend.
-
- 12 Apr, 2011 1 commit
-
-
Joel Martin authored
Issue #21 - non-US keyboard layouts. Only identify some keys as special during the keyDown event so that when using non-US keyboards the values don't overlap with the values for normal keys. Some keys have to still be identified in both keyDown and keyPress since they generate both: backspace and enter for Firefox and Opera, tab for Opera.
-
- 06 Apr, 2011 2 commits
-
-
Joel Martin authored
Also clarify usage statement with legend height adjustment. Remove console.log in arrays.js so that it works in firefox without firebug.
-
Joel Martin authored
-
- 05 Apr, 2011 3 commits
-
-
Joel Martin authored
-
Joel Martin authored
-
Joel Martin authored
This is part of addressing issue #21 - non-US keyboard layouts. There are several challenges when dealing with keyboard events: - The meaning and use of keyCode, charCode and which depends on both the browser and the event type (keyDown/Up vs keyPress). - We cannot automatically determine the keyboard layout - The keyDown and keyUp events have a keyCode value that has not been translated by modifier keys. - The keyPress event has a translated (for layout and modifiers) character code but the attribute containing it differs. keyCode contains the translated value in WebKit (Chrome/Safari), Opera 11 and IE9. charCode contains the value in WebKit and Firefox. The which attribute contains the value on WebKit, Firefox and Opera 11. - The keyDown/Up keyCode value indicates (sort of) the physical key was pressed but only for standard US layout. On a US keyboard, the '-' and '_' characters are on the same key and generate a keyCode value of 189. But on an AZERTY keyboard even though they are different physical keys they both still generate a keyCode of 189! - To prevent a key event from propagating to the browser and causing unwanted default actions (such as closing a tab, opening a menu, shifting focus, etc) we must suppress this event in both keyDown and keyPress because not all key strokes generate on a keyPress event. Also, in WebKit and IE9 suppressing the keyDown prevents a keyPress but other browsers still generated a keyPress even if keyDown is suppressed. For safe key events, we wait until the keyPress event before reporting a key down event. For unsafe key events, we report a key down event when the keyDown event fires and we suppress any further actions (including keyPress). In order to report a key up event that matches what we reported for the key down event, we keep a list of keys that are currently down. When the keyDown event happens, we add the key event to the list. If it is a safe key event, then we update the which attribute in the most recent item on the list when we received a keyPress event (keyPress should immediately follow keyDown). When we received a keyUp event we search for the event on the list with a matching keyCode and we report the character code using the value in the 'which' attribute that was stored with that key. For character codes above 255 we use a character code to keysym lookup table. This is generated using the util/u2x11 script contributed by Colin Dean (xvpsource.org).
-
- 03 Apr, 2011 2 commits
-
-
Joel Martin authored
-
Joel Martin authored
API change: for intergrators that explicitly include the Javascript files (that do not use include/vnc.js)js, include/input.js is a new file that must also be included. The mouse and keyboard handling could be useful on its own so split it out into a Keyboard and Mouse class in include/input.js. This refactoring is preparation to deal with issue #21 - non-US keyboard layouts.
-
- 29 Mar, 2011 2 commits
-
-
Joel Martin authored
-
Joel Martin authored
Fix mouse button mapping in IE9. All browsers have converged on a standard left=0, middle=1, right=2 ... all except IE that is. Add html5 doctype to tests. In vnc_perf test, use do_test instead of start for function name since start is a keyword in IE. In error about Flash give a link to Adobe's download page.
-
- 26 Mar, 2011 1 commit
-
-
Phil Phillips authored
-
- 25 Mar, 2011 1 commit
-
-
Joel Martin authored
-
- 24 Mar, 2011 1 commit
-
-
Joel Martin authored
-