The method was hot-patched into the pythondialog library if it was
missing. Use the same format found in pythondialog 3.x

New versions of python-dialog will create deprecation warnings when
using the old values

Use dialog constants to compare with the return value of yesno(). In
newer versions of the dialog library, the return value of the function
is unicode strings.

The function would raise an exception if the value was not a list

By default the output goes to sys.stdout. This is used in snf-mkimage
to output the plankton answer when registering an image to a synnefo
deployment.

This resolves #21

The base class is named Output. Having a method with the same makes
the code confusing.

This can be used to display the current execution log.

Instead of defining a list member inside.

The type for those parameters is list:<type>

This used to be a class in the util module, but since this is only used
on the Image, it suits better there.

When the user picks a directory that contains VirtIO drivers, show him
the version of the discovered drivers in the confirmation box.

Don't treat shrink as a seperated task. Add it in the syspreps menu.

 * Cleanup Wizard and WizardPage classes in dialog_wizard
 * Fix various pylint warnings

Add a page in the dialog wizard that displays the current state of
the VirtIO drivers of the image and allow the user to update the
installed VirtIO drivers. This page will only be shown if the media
hosts a Windows image.

Make it more general. Till know it was only used for selecting the input
media but other parts of the program should also make use of it.

According to the decision of the GRNET Board of Directors,
switch license to GPLv3.

This commit will be propagated to the release
and master branches based on git flow, and the next
release will be licensed as GPLv3.

Allow the characters that kamaki allows

Make the cloud selection wizard page an instance of WizardMenuPage

When registring an image, use the information returned by the
kamaki register method to construct the metadata file.

When dumping the image to the local filesystem, store the image
properties and the disk-format info in the metadata file.

 * Change the authentication everywhere to use clouds
   (authentication URL and token pairs)
 * Add menu entries to manage clouds
 * Add an extra -a option in snf-image-creator to allow the user to
   specify authentication URLs

 * Prefix all private methods with _
 * Write missing docstrings
 * Move all public methods above the private ones
 * Add module docstrings where missing
 * Define source code encodings on all modules

If the image gets registered as public allow anyone to read the
metadata and the md5sum file.

Rename DiskDevice class to Image and move it to a seperate module.
Also, don't let the user access the os_type/* modules directly. In
Image class create the `os' member variable that will host an
appropriate instance of one of the OSBase classes.

Create a new dialog_menu module to host all the "expert mode" code.
Check the code with a new version of pep8