mirror of
https://gitlab.uni-freiburg.de/opensourcevdi/spice-html5
synced 2025-12-26 04:36:03 +00:00
The previous implementation worked strictly due to a bug which would luckily generate roughly the right scan codes, although we would send more codes than required. For example, the old implementation would send 0xdf48e0 for 'up key down' and '0xdfc8e0' for 'up key up'. The prepended 0xdf is incorrect; the correct values should be 0x48e0 and 0xc8e0. Essentially, it stored the bytes in reverse order and had a bug while flipping them. This code stores them in the order we transmit them which simplifies the code. Signed-off-by: Jeremy White <jwhite@codeweavers.com> Acked-by: Frediano Ziglio <fziglio@redhat.com> |
||
|---|---|---|
| src | ||
| .gitignore | ||
| apache.conf.sample | ||
| COPYING | ||
| COPYING.LESSER | ||
| Makefile | ||
| package.json.in | ||
| README | ||
| spice_auto.html | ||
| spice-html5.spec.in | ||
| spice.css | ||
| spice.html | ||
| TODO | ||
Spice Javascript client
Instructions and status as of August, 2016.
Requirements:
1. Modern Firefox or Chrome (IE will work, but badly)
2. A WebSocket proxy
websockify:
https://github.com/kanaka/websockify
works great.
Note that a patch to remove this requirement has been submitted
to the Spice project but not yet been accepted. Refer to this email:
https://lists.freedesktop.org/archives/spice-devel/2016-June/030552.html
3. A spice server
Optional:
1. A web server
With firefox, you can just open file:///your-path-to-spice.html-here
With Chrome, you have to set a secret config flag to do that, or
serve the files from a web server.
Steps:
1. Start the spice server
2. Start websockify; my command line looks like this:
./websockify 5959 localhost:5900
3. Fire up spice.html, set host + port + password, and click start
Status:
The TODO file should be a fairly comprehensive list of tasks
required to make this client more fully functional.