project: Initial import.
readme: Update.
readme: Update.
optimization: Some minor optimizations.
bugfix: Somehow the wrong version got check in which didn't have a write socket notifier.
pushpull: Added initial (working) version of a PUSH-PULL sample.
usage: Improved usage message and command line parameter handling.
cleanup: Clean up code.
comment: Added code comment.
eventloop: Correctly integrate running commands into Qt's event loop.
pushpull: Example has reached an acceptable final state.
readme: Updated according to new PUSH-PULL sample.
rename,cleanup: Renamed class and executable; cleaned up some code.

--HG--
rename : src/TestApp.h => src/NzmqtApp.h
readme: Fixed typo.
readme: Added link to 'zeromqt'.
fix: Made public method public again.
Disabled QSocketNotifier for writing when nothing is written
readme: Added link to bug tracker.
bugfix,gh-1: Merged bugfix of Jelle Hissink, which fixes gh-1.

Here is the corresponding issue description given by Jelle:

"
When I create a SUB socket on tcp (either localhost or ip) I get continuous notifications on the socketActivity() slot, this prevents QTimer from running correctly.
The source of the continuous calls is in the socketNotifyWrite_ notifier. Inside this call to socketActivity flags() always returns 0 and socketActivity() will be called again immediately flooding the event loop.
I made a small modification to the source to prevent this by disabeling the notifier when flags() returns 0 and enabeling it again if sending fails because sending would block.
"

NOTE: During the merge I ignored line break changes in order to get a clean change set.
.
refactoring: Introduced intermediate 'ZMQSocketBase' class and made getter methods const.