| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Since QRandomGenerator is only available since Qt 5.10, the deprecated
functions are still used for Qt < 5.10.
|
| |
|
|
| |
Co-authored-by: Robert Maerkisch <zatroxde@protonmail.ch>
Co-authored-by: Linus Jahn <lnj@kaidan.im>
|
| |
|
|
| |
This makes creating forms manually a lot easier.
|
| | |
|
| | |
|
| |
|
|
| |
So they don't leak into the public API
|
| | |
|
| |
|
|
|
|
| |
Two new macros were added:
* QBL (short alias for QByteArrayLiteral)
* QSL (short alias for QStringLiteral)
|
| | |
|
| |
|
|
| |
This way we can for example add a server for IPv4 and one IPv6.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 4af8f27d6bcbb44d349f4637d4653ac6ca3de09c.
On the XMPP summit the decision was made to stick to the roster
extension now. The custom protocol would in the end be like a copy of
the roster protocol. Thus, the roster iq extension should not be
removed or replaced with another protocol.
|
| |
|
|
|
|
|
|
|
|
|
| |
This replaces all occurencies of 'slots' and 'signals' with 'Q_SLOTS'
and 'Q_SIGNALS'. This allows for smooth integration with software
projects that need QT_NO_KEYWORDS, such as those ones that rely on
boost libraries.
Closes #115.
Co-authored-by: Tommaso Cucinotta <tommaso.cucinotta@santannapisa.it>
|
| |
|
|
|
|
|
|
|
| |
This updates the MAM implementation to version 0.6.0. The new namespace
is now used (mam:2). There is no compatibility layer with the old
namespace (mam:1) since both ejabberd and prosody have updated their MAM
implementation to support the mam:2 namespace a while ago.
Closes #254.
|
| | |
|
| |
|
|
|
| |
This adds support of XEP-0359: Unique and Stable Stanza IDs in version
0.6.0.
|
| |
|
|
|
|
|
|
|
|
| |
The QXmppUtils::generateStanzaHash() generates UUIDs by default now.
UUIDs are not generated, if the default parameter is changed to a
different value (!= 36). The behaviour is not changed for other values
than 36.
This way all users of QXmpp will automatically start to use UUIDs, if
they use the generateStanzaHash() method.
|
| |
|
|
|
|
| |
This adds support of XEP-0428: Fallback Indication in version 0.1.0.
https://xmpp.org/extensions/xep-0428.html
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This adds two signals to make the result easily available to the user.
|
| |
|
|
|
| |
It uses QSharedDataPointer<> internally, so passing by value is
recommended.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This can be done without any concerns, because the registerType was not
part of any release yet.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This adds utility methods to create an unregistration or a change
password request in one line.
|
| | |
|
| |
|
|
|
|
|
| |
This is the result of:
sed -i 's/writeAttribute("xmlns", /writeDefaultNamespace(/g' \
$(find . -iname "*.cpp" -or -iname "*.h")
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|