aboutsummaryrefslogtreecommitdiffstats
path: root/net-im/qxmpp
Commit message (Collapse)AuthorAgeFilesLines
* - Convert to USES=qmake (and other USES while I'm here)makc2013-11-221-4/+3
| | | | | | | - Add state support - Convert LIB_DEPENDS to new style, adjust USE_QT4 components, etc. Approved by: portmgr (blanket approval)
* - Replace QT_.*_REL with QT_.* in PLIST_SUB.avilla2013-11-171-1/+1
| | | | | | - Adapt plists. With hat on: kde
* Add NO_STAGE all over the place in preparation for the staging support (cat: ↵bapt2013-09-211-5/+2
| | | | net-im)
* - Changed my emailvg2013-07-221-1/+1
| | | | | | - Trim Makefile headers and positions name and surname within Approved by: eadler, rm (mentors)
* - Convert USE_QT_VER=4 and QT_COMPONETS to USE_QT4miwi2012-06-061-2/+1
| | | | Review by: bapt, David Naylor (kde team)
* - update png to 1.5.10dinoex2012-06-011-0/+1
|
* QXmpp is pretty intuitive and easy to use. It uses Qt extensively.pawel2012-01-128-0/+614
Qt is the only third party library it is dependent on. Users need to a have working knowledge of C++ and Qt basics (Signals and Slots and Qt data types). The underlying TCP socket and the XMPP RFCs (RFC3920 and RFC3921) have been encapsulated into classes and functions. Therefore the user would not be bothered with these details. But it is always recommended to the advanced users to read and enjoy the low level details. WWW: http://code.google.com/p/qxmpp/ PR: ports/163967 Submitted by: Gvozdikov Veniamin <g.veniamin@googlemail.com>