README files should include at least a basic description of what it's all about. Filled them in.

6 files changed, 33 insertions, 6 deletions

diff --git a/ClientHamr/BVJ/README b/ClientHamr/BVJ/README
index c65cc1f..44157cd 100644
--- a/ClientHamr/BVJ/README
+++ b/ClientHamr/BVJ/README
@@ -1 +1,7 @@
-Refer to - http://wiki.infinitegrid.org/index.php/BVJ
\ No newline at end of file
+Refer to - http://wiki.infinitegrid.org/index.php/BVJ
+
+BVJ is extensions to the BVH animation format used by SL technology. 
+It's in the ClientHamr section coz on the server side, they are just
+dealt with as blobs to be sent to the viewers.  This may change if we
+implement animating link sets, and interaction with the sim physics.
+
diff --git a/ClientHamr/IAE/README b/ClientHamr/IAE/README
index fd569ff..48b7935 100644
--- a/ClientHamr/IAE/README
+++ b/ClientHamr/IAE/README
@@ -1 +1,4 @@
-Refer to - http://wiki.infinitegrid.org/index.php/InworldAnimationEditor
\ No newline at end of file
+Refer to - http://wiki.infinitegrid.org/index.php/InworldAnimationEditor
+
+IAE is an idea to put an animation editor in world, much like the link set editor.
+
diff --git a/ClientHamr/README b/ClientHamr/README
index c3bee1f..af3a745 100644
--- a/ClientHamr/README
+++ b/ClientHamr/README
@@ -1 +1,7 @@
-Refer to - http://wiki.infinitegrid.org/index.php/ClientHamr
\ No newline at end of file
+Refer to - http://wiki.infinitegrid.org/index.php/ClientHamr
+
+ClientHamr is the concept that we can apply the unix philosophy to the
+viewer.  Use individual tools that are good at their job to split off
+bits of the big bad blob that is the viewer.  Using standard protocals
+and tools where we can.
+
diff --git a/ClientHamr/XMPP/README b/ClientHamr/XMPP/README
index 747fdcd..d85ecb3 100644
--- a/ClientHamr/XMPP/README
+++ b/ClientHamr/XMPP/README
@@ -1 +1,5 @@
-Viewer integration with XMPP, and using it for as many services as it can.
\ No newline at end of file
+Viewer integration with XMPP, and using it for as many services as it can.
+
+XMPP / jabber is a good protocol to base presence, IM, groups, and other
+related stuff on.  We should do so.
+
diff --git a/ClientHamr/libpurple/README b/ClientHamr/libpurple/README
index f834a30..f86870b 100644
--- a/ClientHamr/libpurple/README
+++ b/ClientHamr/libpurple/README
@@ -1 +1,5 @@
-Viewer integration with libpurple, using it for generic IM services.
\ No newline at end of file
+Viewer integration with libpurple, using it for generic IM services.
+
+Libpurple is  amodular IM system, we could just add a libpurple based IM
+system to the viewer, and use that for the XMPP integration.
+
diff --git a/ClientHamr/mumble/README b/ClientHamr/mumble/README
index ae19c44..6c7984a 100644
--- a/ClientHamr/mumble/README
+++ b/ClientHamr/mumble/README
@@ -1 +1,5 @@
-Viewer integration with mumble and vwhisper, and using it for as many audio services as it can.
\ No newline at end of file
+Viewer integration with mumble and vwhisper, and using it for as many audio services as it can
+
+Mumble is a voice system designed for networked 3D game usage.  Sounds
+perfect, just what we need.  B-)
+