summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGerd Hoffmann <kraxel@redhat.com>2010-09-27 18:09:57 +0200
committerGerd Hoffmann <kraxel@redhat.com>2010-09-27 18:09:57 +0200
commit5fbbe6c04642f40bebc91d91ab1ec85280cfdabf (patch)
treec27836fb5996d18689b5cffa75110b6aec0e2d05
parent7971f6927a21f2c1039edf397b57277591f665a9 (diff)
update README.
-rw-r--r--gtk/README44
1 files changed, 23 insertions, 21 deletions
diff --git a/gtk/README b/gtk/README
index 4bce1ac..8e00a5b 100644
--- a/gtk/README
+++ b/gtk/README
@@ -5,24 +5,6 @@ spice & gtk
Porting spice client to gtk ...
-current state
--------------
-
-spicy app starts becoming usable.
-
-Library API is far from being stable. Likewise the ABI of course.
-If you play with the libs make sure you rebuild everything after
-updating the library for the time being.
-
-Some features are missing:
- - No sound recording support.
- - No client migration support.
- - No mm time handling.
- - Most channel implementations are incomplete.
- - Almost no documentation.
- - Probably more ...
-
-
What you can find here
----------------------
@@ -33,7 +15,7 @@ libspice-client-glib
* Various Spice<Type>Channel (see channel-<type>.h).
libspice-client-pulse
- provides glib objects for sound support via pulseaudio.
+ provides glib object for sound support via pulseaudio.
* SpicePulse (see spice-pulse.h)
libspice-client-gtk
@@ -41,8 +23,28 @@ libspice-client-gtk
* SpiceDisplay (see spice-widget.h)
spicy
- gtk based spice client app.
+ gtk based spice client app. Command line options are simliar
+ to the spicec ones.
snappy
- cmd line tool, connects to spice server and writes out screen shots.
+ Command line tool, connects to spice server and writes out a
+ screen shot.
+
+
+current state
+-------------
+
+spicy app starts becoming usable.
+
+Library API is far from being stable. Likewise the ABI of course.
+If you play with the libs make sure you rebuild everything after
+updating the library for the time being.
+
+Some features are missing:
+ - No sound recording support.
+ - No client migration support.
+ - No mm time handling.
+ - Most channel implementations are incomplete.
+ - Almost no documentation.
+ - Probably more ...