aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* QXmppStreamFeatures: Fix wrong \param commandLinus Jahn2020-02-061-3/+3
|
* Fix undocumented Q_PROPERTiesLinus Jahn2020-02-0414-90/+117
|
* Fix missing documentation for for QXmppStanza::ErrorLinus Jahn2020-02-042-34/+70
|
* Fix doxygen warnings about missing titles for \defgroupLinus Jahn2020-02-042-4/+23
|
* Refactor QXmppRegisterIq: Replace registerType by two separate attr.Linus Jahn2020-02-042-51/+66
| | | | | This can be done without any concerns, because the registerType was not part of any release yet.
* Add new QXmppRegistrationManagerLinus Jahn2020-02-044-5/+669
|
* QXmppStreamFeatures: Fix documentation is not generatedLinus Jahn2020-02-031-0/+4
|
* QXmppStreamFeatures: Fix register feature is enabled by defaultLinus Jahn2020-02-031-1/+2
|
* Run clang-format also on all cpp filesLinus Jahn2020-02-0372-2088/+1535
|
* clang-format: Enable regrouping and sorting of includesLinus Jahn2020-02-03123-345/+384
|
* QXmppRegisterIq: Add utility methods to create common requestsLinus Jahn2020-02-032-1/+40
| | | | | This adds utility methods to create an unregistration or a change password request in one line.
* Fix that no documentation is generated for QXmppStanza::ErrorLinus Jahn2020-02-021-0/+3
|
* Replace manual xmlns writing by writeDefaultNamespace()Linus Jahn2020-01-2936-90/+90
| | | | | | | This is the result of: sed -i 's/writeAttribute("xmlns", /writeDefaultNamespace(/g' \ $(find . -iname "*.cpp" -or -iname "*.h")
* QXmppClient: Remove obsolete methods for TLS managementLinus Jahn2020-01-292-45/+0
| | | | | | | | | | The methods are obsolete since the TLS manager has become an internal client extension. The methods were not of any use except for the TLS manager and should better not be public to the user at all (i.e. startSocketEncryption()). This can be done without any concerns because the methods were not part of the public API in any release, yet.
* Make QXmppTlsManager an internal client extensionLinus Jahn2020-01-294-10/+27
| | | | | | | | | | | This removes the QXmppTlsManager from the public API and makes it an internal client extension. It was not of any use for the end user and was configured via the QXmppClient (as before). This way we can obsolete some public methods of the QXmppClient, that also have been added with the new TLS manager. This can be done without any concerns because the manager was not part of the public API in any release, yet.
* Introduce QXmppInternalClientExtensionsLinus Jahn2020-01-294-0/+104
| | | | | | | | | | | | The new internal client extensions can be used to access private parts of the QXmppClient since QXmppInternalClientExtensions are a friend of the QXmppClient. The internal client extensions are not part of the public API, so you can't access them in an application using QXmpp. However, this was also the case before. If there is the need to access the internal extensions in the future, we'll still have all options open to change everything, because the classes are not part of the public API.
* QXmppClient: Split up QXmppClientPrivate into private headerLinus Jahn2020-01-292-25/+78
| | | | | | | This is required to access the QXmppClientPrivate from other classes. This way we can split up parts of the client into internal client extensions like the authentication manager, without the need of public methods in the client as with the current approach of the TLS manager.
* Update copyright notice in missing filesLinus Jahn2020-01-284-4/+4
|
* server: Replace manual checks and hard-coded XML by QXmppStartTlsPacketLinus Jahn2020-01-203-33/+19
|
* Move TLS negotiation into new QXmppTlsManagerLinus Jahn2020-01-206-43/+170
|
* Add QXmppStartTlsPacket to replace hard-coded XML in TLS codeLinus Jahn2020-01-203-0/+167
|
* Port majority of old-style connects (#237)JBB2020-01-2020-445/+231
| | | This provides more type safety and is future-proof.
* QXmppClient: Add missing '\since' tag to new indexOfExtension()Linus Jahn2020-01-191-3/+4
| | | | I forgot this in #241.
* QXmppRegisterIq: Do not pass registerType by const-refLinus Jahn2020-01-192-2/+2
|
* QXmppRegisterIq: Add missing '\since' tags to new methodsLinus Jahn2020-01-192-0/+8
| | | | I forgot them in #240.
* QXmppClient: Add method to get index of extensionLinus Jahn2020-01-131-0/+24
|
* QXmppRegisterIq: Add registerType for registered/removeLinus Jahn2020-01-132-2/+57
|
* Bump copyright year to 2020Linus Jahn2020-01-06158-158/+158
|
* Add a .clang-format somewhat close to the current style0xd34df00d2019-12-2366-587/+554
|
* QXmppGlobal: Use QT_VERSION_CHECK() to generate QXMPP_VERSIONLinus Jahn2019-12-181-1/+1
| | | | | | | | | QT_VERSION_CHECK() returns the same format as is currently used, it is easier to read and fixes a problem that could occur with the previous marco. The macro was unenclosed causing comparison to fail. This also happened in Kaidan [1]. [1]: https://invent.kde.org/kde/kaidan/commit/5a3e5e8a748488f4d55302b4beacce880dde381a
* Refactor QXmppPresence, Add missing testsLinus Jahn2019-12-102-256/+238
|
* Refactor QXmppPubSubIq and add missing testsLinus Jahn2019-12-083-25/+28
|
* Split up QXmppPubSubItem from QXmppPubSubIq.hLinus Jahn2019-12-085-95/+164
|
* QXmppPubSubIq/QXmppPubSubItem: Use d-pointer to maintain binary compat in futureLinus Jahn2019-12-082-51/+95
|
* Replace emails in copyright headers by entries in the AUTHORS fileLinus Jahn2019-12-0810-10/+10
| | | | Mostly this was a mistake by me in earlier contributions.
* Implement XEP-0231: Bits of Binary: register IQ extensionLinus Jahn2019-12-062-0/+44
| | | | | This adds support for XEP-0231: Bits of Binary attachments in registration forms.
* Implement XEP-0231: Bits of Binary: message extensionLinus Jahn2019-12-062-0/+50
| | | | This adds support for XEP-0231: Bits of Binary attachments in messages.
* Implement XEP-0231: Bits of Binary: stanza extensionLinus Jahn2019-12-063-0/+111
| | | | | | This adds a type that may be used as a stanza extension. It is useful, when a stanza contains (possibly multiple) XEP-0231: Bits of Binary data elements.
* Implement XEP-0231: Bits of Binary: IQLinus Jahn2019-12-065-0/+368
| | | | | This implements parsing and serialization of the BoB IQ from XEP-0231: Bits of Binary in version 1.0.
* Implement XEP-0231: Bits of Binary: content identifiersLinus Jahn2019-12-063-0/+304
| | | | | This implements parsing and serialization of content identifiers from XEP-0231: Bits of Binary in version 1.0.
* QXmppRegisterIq: Use d-pointer to maintain binary compat in futureLinus Jahn2019-12-062-33/+57
|
* QXmppClient: Set correct CSI state on connectLinus Jahn2019-11-281-2/+7
|
* QXmppClient: Only send CSI state when connectedLinus Jahn2019-11-281-1/+1
|
* Replace deprecated Q_ENUMS with Q_ENUMLinus Jahn2019-10-277-24/+20
| | | | | Q_ENUM exists since Qt 5.5, more details can be found here: https://woboq.com/blog/q_enum.html
* QXmppMucManager: Only return true if actually handled stanzaMartin Koller2019-10-271-3/+4
|
* Remove Qt < 5.7 compatibility codeLinus Jahn2019-10-231-13/+0
|
* Replace Q_FOREACH (foreach) by C++11 ranged for-loopsLinus Jahn2019-10-2332-197/+179
| | | | | | | Q_FOREACH is bad and will be deprecated in the future: https://www.kdab.com/goodbye-q_foreach/ This also disables Q_FOREACH by defining QT_NO_FOREACH.
* Add \since QXmpp 1.1 to all new methods and classesLinus Jahn2019-10-239-2/+80
| | | | Methods of new classes have no \since tag.
* Refactor data form media elementLinus Jahn2019-10-232-45/+313
| | | | | | | | | | | * Add QXmppDataForm::MediaSource instead of using a QPair<QString, QString> to save the URIs and content types. * Deprecate QXmppDataForm::Media: The extra class was useless: Each Field has exactly one media element and the media element has only two attributes (size and media sources) * Add mediaSources and mediaSize attributes to the QXmppDataForm::Field * Deprecate getters/setters for the Media element of QXmppDataForm::Field (they are still working and tested)
* Port away from deprecated client extension getters of the QXmppClientLinus Jahn2019-10-235-37/+53
| | | | | This replaces the deprecated getters in the examples and in the documentation.