[Spice-devel] Embedding the Spice Client in Windows
Marc-André Lureau
mlureau at redhat.com
Fri Mar 7 15:05:18 PST 2014
----- Original Message -----
> On Fri, 7 Mar 2014 09:08:20 AM Marc-André Lureau wrote:
> > What you are interested in is the spice-glib library:
> >
> > http://elmarco.fedorapeople.org/spice-gtk/ch02.html
>
>
> Thanks Marc-André, that looks much simpler than I thought it would, I don't
> anticipate any issues wrapping the base api into Qt classes.
>
> However :) I only have a passing acquaintance dealing with video buffers and
> audio streams, so I will be drawing on the lists expertise when the time
> comes.
>
> Quick question to display my ignorance. I presume the imgdata buffer provided
> in the "display-primary-create" signal is the raw image data, and it is up to
> the actual qt widget to display that data, interpreting the display format
> (SPICE_SURFACE_FMT_32_xRGB or SPICE_SURFACE_FMT_16_555).
>
> Updates to the buffer are signaled via "display-invalidate".
> Actual transfer of data from the vm guest to the spice buffer (imgdata) is
> handled by the library behind the scenes and I don't have to worry about that
> side of things?
That's all correct. Qt runs of top of glib mainloop nowadays, afaik, so spice-glib should do its io and tasks in the background.
You can call then call the session & channel APIs and connect to the signals to send events or reacts to them.
I can't wait to see your progress on this!
cheers
More information about the Spice-devel
mailing list