providers.md in veewee-0.3.9

- old
+ new
@@ -1,23 +1,8 @@
-# Providers in Veewee
+# Veewee Virtual Machine Providers
 
-Initially veewee started as provider for virtualbox. From v0.3 Vmware fusion and KVM support are introduced.
+Veewee now has multiple virtual machine (VM) providers. Initially Veewee started with only VirtualBox as a provider. VMware Fusion and KVM were introduced in v0.3.  Parallels support is the newest addition.
 
-## Virtualbox
-
-To interact with virtualbox, veewee executes shell-commands through the 'VboxManage' command. The virtualbox gem library proved to be less stable.
-
-To simulate the typing, veewee uses the 'VBoxManage controlvm 'myubuntu' keyboardputscancode <keycode>'.
-Scancode are injected directly the keyboard buffer with this. And as this buffer is small, we can't type fast.
-This is why you have the delay while veewee types the commands. Speeding it up, will make the keyboard buffer loose keystrokes.
-
-## Vmware fusion
-
-To interact with Vmware fusion, we leverage (a currently patched) version of [Fission gem](https://github.com/thbishop/fission). This takes care of the heavy lifting.
-
-To interact with the screen , veewee enables VNC on the created vmware fusion machines and use the [Ruby-VNC gem](http://code.google.com/p/ruby-vnc/) to send the keystrokes. Here too , sending keystrokes too fast is a problem.
-
-## KVM
-
-To interact  with KVM veewee, uses [libvirt support](http://libvirt.org/ruby/) provided through [Fog gem](http://fog.io).
-
-To interact with the screen , veewee enables VNC on the created kvm machines and use the [Ruby-VNC gem](http://code.google.com/p/ruby-vnc/) to send the keystrokes. Here too , sending keystrokes too fast is a problem.
+* [Guide for VirtualBox](vbox.md)
+* [Guide for VMware Fusion](fusion.md)
+* [Guide for KVM](kvm.md)
+* [Guide for Parallels](parallels.md)