Explicitly include the Qt use file again.
Added qRestAPI as an external project.
Moved the XNAT clases from the org.commontk.xnat plug-in.
Moved the XNAT classes into a Core subdirectory.
Added XNATWidgets library stub.
Removed unused XNAT files and simplified QtScript dependency.
Added initial ctkXNATBrowser application.
Login dialog added
qRestAPI upgrade
Fix for compiler warnings
ctkXnatObject redesign. No QObjects, using QSharedPointer.
Qt list model for ctkXnatObject instances. Will be renamed.
Prototype application for querying XNAT servers.
Fix slider unit tests with tiny single steps

Such single steps should not be allowed as they would prevent the original
double value from being retrieved with an integer.
Fix ctkDoubleSpinBoxTest when setting range to the smallest double
Fix ctkRangeSliderTest when run with different styles

The test was written using QCleanlooks style and it fails with GTK style.
Add value proxies

Value proxies are functions that can be set on widgets representing
numbers such as ctkDoubleSpinBox, ctkDoubleSlider... The proxies decouple
the values displayed from the input value.

For example, one might want to manipulate celsius in the code but to
display fahrenheits. In that case, a "celsius to fahrenheit" linear value
proxy can be added to the widget. The displayed values will be in
fahrenheit while the value given by the widget signals and accessors will
be give celsius.

Note, the minimum, maximum, single step and decimals apply on the spinbox
displayed value. If the spinbox limit is 200 and the proxy value a function
like f(x) = x - 30, then one can call setValue(212) on the widget. The
value displayed will be 182 and the signal valueChanged will give 212.
A setValue(256) however will be have a display value of 200 and the signals
valueChanged give 230.

The base class for value proxies is ctkValueProxy. Subclasses should
reimplement the methods valueFromProxyValue() and proxyValueFromValue().
Propagate value proxy to other widgets

Adding the value proxy to:
 - ctkDoubleSlider
 - ctkSliderWidget
 - ctkCoordinatesWidget
 - ctkRangeWidget
 - ctkDoubleRangeSlider

For the ctkSliderWidget, since it's using the ctkDoubleSlider and the
ctkDoubleSpinBox, we can simply pass the value proxy to these. The same
thing applies to ctkCoordinatesWidget.
For the others, it's like the ctkDoubleSpinBox. The proxy is set between
the values accessors.

The tests added are very similar to the ctkDoubleSpinBox test, just tweaked
to these classes specific API.
Update displayed value when value proxy is modified
Cleanup ctkWorkflowButtonBoxWidget

* factorize/simplify code
* add comments
* use deleteLater instead of delete:
deleteLater is safer. It only deletes the object next time it gets into
the event loop again. There is then no danger of having a slot trying to
access the deleted object. See:
http://stackoverflow.com/questions/4888189/how-delete-and-deletelater-works-wrt-to-signals-and-slots-in-qt