[Spice-devel] Announcing spice-xpi 2.5

Bitman Zhou bitman.zhou at sinobot.com.cn
Fri Jun 10 00:04:43 PDT 2011

Here is an example html:

<!DOCTYPE html>
<title>SPICE Plugin Test</title>
<script type="text/javascript">
	function connectvm()
		var ip = String("");
		var port = String("5901");
		var passwd = String("pass at 321");
		var pluginobj = document.embeds[0];

		pluginobj.hostIP = ip;
		pluginobj.port = port;
		pluginobj.Password = passwd;
		pluginobj.fullScreen = true;
		pluginobj.UsbListenPort = 0;
    	<embed type="application/x-spice">
        <button onclick='connectvm()'>connect to VM</button>
        	If the plugin is working correctly, a click on the button
should open spice client.

I also verified this plugin works well with Google Chrome browser, at
least on my Ubuntu 11.04 x86_64 system.

Bitman Zhou

在 2011-06-10五的 08:55 +0200,Hans de Goede写道:
> Hi,
> On 06/10/2011 12:27 AM, Scott Dowdle wrote:
> > Peter,
> >
> > ----- Original Message -----
> >> I am glad to announce the first public free open source software release
> >> of the spice-xpi. To download the source tarballs, visit the page
> >> http://www.spice-space.org/download.html
> >
> > The description of spice-xpi on that page says:
> >
> > "Spice-XPI plugin for mozilla plugin compatible browsers. This is used for launching the spice client from the RHEV-M user portal."
> >
> > I would assume that the URL one clicks on in the RHEV-M user portal contains the same basic info that spicec would use to connect to a remote KVM VM via SPICE... host, port, password, and cert?  If so, is there some documentation somewhere that specifies how one constructs the URL?  I don't currently have access to RHEV for Desktops to see what the URLs look like.
> >
> > I know the source code to spice-xpi is the ultimate documentation... and I looked at the contents of the .tar.gz file... for the various documentation that might be included with the source.  I didn't find much info... and I'm not programmer-ish enough to look directly at the source to piece the info together.
> >
> I'm afraid that I'm not familiar enough with the exact usage to answer
> this thoroughly. How the plugin basically works is
> that you embed it, then through js on the object you
> set a number of properties (which can include ssl certs)
> and then you tell it to connect, and it will then
> start the spice-client (currently it uses spicec not one
> of the spice-gtk based clients) and pass in all needed /
> provided info.
> Perhaps someone else can provide a more thorough answer ...
> If someone figures this out on his own, please write a short
> text about this, so we can include it with the next release
> of the XPI and put it on the wiki.
> Thanks & Regards,
> Hans
> _______________________________________________
> Spice-devel mailing list
> Spice-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel

More information about the Spice-devel mailing list