| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
list a bit, but it is overall working pretty well. Added ng-infinite-scroll-matrix.js and jquery-1.8.3 as deps.
|
| |
|
|
| |
Make eventStreamService manage it's own repolling provided no one calls stop() on it. Couple the stream with eventHandlerService so any controller can just blithely call eventStreamService.resume() and expect to 'get stuff' without having to handle promises (though resume() still returns a promise for that request and proxies it through $q). Kill and reset the stream if you logout.
|
| |
|
|
| |
$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.
|
| |
|
|
| |
the event stream. This depends on matrix service to do the actual hit. Currently this has exactly the same behaviour as before.
|
| |
|
|
| |
promise and not a wrapped one via $q. Everything now needs a level deeper nesting. Fixed registration and login.
|
| | |
|
| |
|
|
| |
rather than top-to-bottom. makes the overscroll much more predictable and sane and not dependent on CSS expressions.
|
| |
|
|
| |
copyrighter.pl whilst we're at it
|
| |
|
