2013-03-19 09:00:38 -05:00
2012-06-04 17:22:01 +03:00
2013-02-11 09:17:53 -06:00
2012-06-04 17:22:01 +03:00
2012-06-04 17:22:01 +03:00
2012-06-04 17:22:01 +03:00
2012-06-04 17:22:01 +03:00
2013-03-19 08:57:51 -05:00
2013-03-19 09:00:38 -05:00
2012-06-04 17:22:01 +03:00
2012-06-04 17:22:01 +03:00
2013-03-08 13:56:36 -06:00
2012-06-04 17:22:01 +03:00
2013-03-19 09:00:38 -05:00
2012-06-04 17:22:01 +03:00
2012-06-04 17:22:01 +03:00
2013-02-11 09:17:55 -06:00
2012-06-04 17:22:01 +03:00

Prototype Spice Javascript client

Instructions and status as of June 1, 2012.

Requirements:

  1.  Modern Firefox or Chrome
      
  2.  A WebSocket proxy

      I've used websockify:
        https://github.com/kanaka/websockify
      works great.


  3.  A spice server

      At this point, I've tested with qemu hosting
      a Fedora image, a Vista image, and with Xspice.  
      Vista was pretty bad; I recommend either Linux or Xspice.

      ** Xspice has a processing issue; see this email:
         http://lists.freedesktop.org/archives/spice-devel/2012-May/009020.html


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.

  As of June 1, 2012, this client is a nifty proof of concept,
  but a long way from being a useful production tool.
Description
RETIRED, further work has moved to Debian project infrastructure
Readme 440 KiB
Languages
JavaScript 93.3%
HTML 5%
CSS 0.9%
Makefile 0.8%