gergely/matrix-glib-sdk
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
GLib based library to communicate with Matrix.org homeservers
335 Commits 4 Branches 1 Tag 1.3 MiB
C 93%
Vala 5.7%
Meson 0.8%
Objective-C 0.5%
fcc592b072
Go to file
Gergely Polonkai fcc592b072 Fix state and room events 
* State event descended from Event, but it is actually based on Room
* Room events may have a missing room_id property due to HS
* optimization
2016-03-16 17:13:05 +01:00
docs Remove final traces of old documentation 2016-03-05 07:35:20 +00:00
m4 Update autotools to Vala usage 2016-03-04 14:00:06 +01:00
src Fix state and room events 2016-03-16 17:13:05 +01:00
vapi Move internal vapis to a separate directory 2016-03-05 07:35:55 +00:00
.gitignore Create the Profile object 2016-03-14 23:09:08 +00:00
AUTHORS Add AUTHORS, NEWS and README files 2016-02-22 14:54:15 +01:00
autogen.sh Move documentation generating to Valadoc 2016-03-04 14:52:22 +01:00
configure.ac Move namespace-info.vala to namespace-info.vala.in 2016-03-10 19:08:33 +01:00
COPYING Add COPYING file 2016-02-21 23:17:35 +01:00
Makefile.am Move documentation generating to Valadoc 2016-03-04 14:52:22 +01:00
NEWS Add AUTHORS, NEWS and README files 2016-02-22 14:54:15 +01:00
README Add AUTHORS, NEWS and README files 2016-02-22 14:54:15 +01:00
README.md Update README.md 2016-01-13 22:45:35 +01:00
vala-globals.mk Move internal vapis to a separate directory 2016-03-05 07:35:55 +00:00

README.md

Matrix Client SDK for GLib

This is a Matrix.org client-server SDK for GLib >= 2.40. It contains both raw API calls and a signal based asynchronous client. The API and ABI are both very volatile as of now; don’t rely on any specific feature until the API is frozen.

The main interfaces are MatrixAPI and MatrixClient. MatrixHTTPAPI and MatrixHTTPClient implement these interfaces, respectively and can communicate with an HTTP based homeserver. If a new protocol becomes supported oficially, a new API and Client class will be added.

Usage

The SDK provides two layers of interaction. The low-level layer (MatrixAPI implementations like MatrixHTTPAPI) just wraps the raw API calls. The high-level layer (MatrixClient implementations like MatrixHTTPClient) is a GMainLoop based asynchronous object that emits GObject signals and uses the low-level layer to provide an object model to perform actions on.

Client

The MatrixClient interface is not fully planned yet.

API

For a full blown example, see test-client.c.