aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2016-05-06Use lambda captures instead of throwing job pointers aroundKitsune Ral
2016-05-06Enhanced logging of job failuresKitsune Ral
2016-05-06Make sure the QNetworkReply object is aborted at any failure and even silent ↵Kitsune Ral
destruction of the job
2016-05-06Add separate success() and failure() signals to BaseJobKitsune Ral
This is to facilitate processing of job results (see further commits).
2016-05-03Merge pull request #4 from KitsuneRal/user-room-names2Felix Rohrbach
Render display names of users and rooms according to the spec - take 2
2016-05-02Actually connect User::nameChanged to Room; make a new Room::memberRenamed ↵Kitsune Ral
signal, which clients should use in the room context. Processing changes of user displaynames is tricky: we have to not only deal with the currently renamed user but also with its past and new namesakes which might change representation due to that renaming. So in the worst case a single User::nameChanged signal may lead to three Room::memberRenamed references (and 3 user displaynames updated in the UI, respectively). And the newly added users should be taken care of in a similar manner, of course.
2016-05-02Reworked room name calculation to get rid of do {} while (false)Kitsune Ral
(as requested at PR review)
2016-05-02Calculate room displayname according to CS spec, with a new signal fired on ↵Kitsune Ral
a displayname update. This changes the way displayname is supplied to a client application - instead of calculating immediately, displayname becomes a separate stored value that is refreshed with every change of the list of members, or the name, or the canonical alias. displaynameChanged signal is supplied to subscribe to these updates: in case of displaying a room in the roomlist a client should use this new signal instead of Room::namesChanged. The displaname calculation algorithm is described in section 11.2.2.5 of the CS spec: https://matrix.org/docs/spec/r0.0.1/client_server.html#calculating-the-display-name-for-a-room
2016-05-02Introduced Room::roomMemberName(User*) that follows CS spec section 11.2.2.3Kitsune Ral
2016-05-02Mark read-only accessors in Room::Private as const.Kitsune Ral
2016-05-02Change the way room members are stored to the one recommended by the CS spec.Kitsune Ral
According to section 11.2.2.3 of the CS spec, clients SHOULD follow a certain algorithm of making a non-ambiguous display name of a user in the room context. This algorithm implies checking whether other room members have the same display name. This commit prepares for implementation of the algorithm: 1. Use a hash map instead of a list to store room members. The external Room::users() API is kept intact. 2. Convenience CRUD methods are implemented to deal with the hash map. 3. An additional slot for user renaming is introduced (because renaming affects the hash map). Binding of actual signals is left for the next commit. 4. nullptr is the recommended representation of a null pointer since C++11. Use that and mandate compiler support of that.
2016-05-02Deduplicated room check-and-creation code.Kitsune Ral
2016-05-02Store left room members as well.Kitsune Ral
In particular, this will be needed to render room names according to the CS spec.
2016-05-02Supply more information with User::nameChanged signalKitsune Ral
2016-05-01Merge pull request #3 from davidar/masterFelix Rohrbach
Resolve Matrix SRV records.
2016-04-23Room: Q_INVOKABLEDavid A Roberts
2016-04-22Allow login with token.David A Roberts
2016-04-12Merge remote-tracking branch 'upstream/master'David A Roberts
2016-04-12Resolve Matrix SRV records.David A Roberts
2016-04-11Merge pull request #2 from KitsuneRal/code-maintenanceFelix Rohrbach
Code maintenance
2016-04-11Rename package.priDavid A Roberts
2016-04-11Add QMake project include file.David A Roberts
2016-04-11Add more target_compile_features supported by CMake 3.1 and already used in ↵Kitsune Ral
the code. See https://cmake.org/cmake/help/v3.1/prop_gbl/CMAKE_CXX_KNOWN_FEATURES.html#prop_gbl:CMAKE_CXX_KNOWN_FEATURES for the full list. All the newly added features are already implied by C++11 standard so for older CMakes -std=c++11 should cover all bases anyway.
2016-04-11Factor out the code that searches an insertion point in a timeline.Kitsune Ral
This is used once in the library and, I guess, twice more in the Quaternion. Implemented as a template function that is equally suitable for Event and Message, and any container that supports STL-style iterators (QList and other Qt containers do).
2016-04-11Drop unneeded check and debug messageKitsune Ral
2016-04-11Use a more telling log line than !!!!Kitsune Ral
2016-04-11Don't put excess whitespaces in log lines before QStrings - Qt inserts them ↵Kitsune Ral
automatically.
2016-04-11Minor fixes and cleanupKitsune Ral
1. Remove accidental trailing \ 2. Show the contents of NetworkError in logs
2016-04-11Missing method in the last commitFelix Rohrbach
2016-04-09Implement different types of messagesFelix Rohrbach
2016-04-09Merge pull request #1 from davidar/masterFelix Rohrbach
Make Connection parent of Room.
2016-04-09Make Connection parent of Room.David A Roberts
2016-04-08Merge pull request #1 from davidar/masterKitsuneRal
Allow Connections to be used in QML.
2016-04-08Rename Room::messages to Room::messageEventsKitsune Ral
Originally by Felx Rohrbach (kde@fxrh.de)
2016-04-08Use class instead of struct to remove warningKitsune Ral
Originally by Felix Rohrbach (kde@fxrh.de)
2016-04-07Allow Connections to be used in QML.David A Roberts
2016-04-05CMakeLists to build a (so far only static) library.Kitsune Ral
2016-04-05KCoreAddons imported.Kitsune Ral
2016-04-05Took README.md from Quaternion, with minor redactions.Kitsune Ral
2016-04-05Added .gitignoreKitsune Ral
2016-04-05Imported the current source tree from Quaternion/lib.Kitsune Ral
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 17:59:17 +0000