Emmanuel ROHEE
|
828101dd51
|
Represent user power level in a room by a red bar at the bottom of his avatar image. The width of this bar depends on the power level.
|
2014-09-02 11:54:35 +02:00 |
|
David Baker
|
5308e3026a
|
Change call signalling messages to be their own types of room events rather than room messages with different msgtypes: room messages should be things that the client can display as a unit message to the user.
|
2014-08-29 13:23:01 +01:00 |
|
David Baker
|
171d8b032f
|
Merge branch 'voip' into develop
Conflicts:
webclient/room/room-controller.js
|
2014-08-29 11:33:36 +01:00 |
|
Emmanuel ROHEE
|
7c99ebdbd1
|
Added waitForInitialSyncCompletion so that clients can know when they can access to the data retrieved by the initialSync Request
|
2014-08-28 16:23:30 +02:00 |
|
David Baker
|
7d34a1c108
|
WIP voip support on web client
|
2014-08-27 18:57:54 +01:00 |
|
Kegan Dougal
|
5796232cb1
|
Adjusted webclient to use new state paths. Updated membership msg template to actually show the person invited. Factored out common membership functions in matrix service.
|
2014-08-26 10:24:47 +01:00 |
|
Erik Johnston
|
6118a102c1
|
Keep track of people's presence and query that when we update the members list.
|
2014-08-22 10:51:00 +01:00 |
|
Erik Johnston
|
74c90f7815
|
Reinitialize room when creating a RoomController so that we start off with a clean slate, as it expects/
|
2014-08-22 10:51:00 +01:00 |
|
Matthew Hodgson
|
3277a65052
|
actually display room metadata based on m.room.membe events
|
2014-08-21 19:02:00 +01:00 |
|
Kegan Dougal
|
02e45da895
|
When new invites come down, update the My Rooms list. Added hacks to make the display name a bit nicer (/im/sync needs to return room aliases / membership events better)
|
2014-08-15 17:42:11 +01:00 |
|
Kegan Dougal
|
c51cf4efca
|
Store messages in $rootScope so they can be accessed from multiple controllers without duplicated storage for each. This also gives updates.
|
2014-08-15 14:06:56 +01:00 |
|
Kegan Dougal
|
5dbceaf5a4
|
Added event handler service which.. handles events. More specifically, it $broadcasts events depending on their type, and does processing on events (shuffling keys, adding events to $rootScope so displays will automatically update, sending delivery receipts, and so on). Some of this logic was previously contained in the RoomController, which fails the moment you add >1 room into the mix, hence requiring a Service to handle events, rather than having each individual controller maintain their part of the world.
|
2014-08-15 14:06:56 +01:00 |
|