Mikael Nordfeldth
b596391fcd
Avoid having to check for notices without rendered copies in upgrade.php
|
%!s(int64=9) %!d(string=hai) anos | |
|---|---|---|
| .. | ||
| actions | %!s(int64=11) %!d(string=hai) anos | |
| classes | %!s(int64=9) %!d(string=hai) anos | |
| css | %!s(int64=10) %!d(string=hai) anos | |
| js | %!s(int64=10) %!d(string=hai) anos | |
| locale | %!s(int64=9) %!d(string=hai) anos | |
| scripts | %!s(int64=9) %!d(string=hai) anos | |
| Makefile | %!s(int64=10) %!d(string=hai) anos | |
| README | %!s(int64=13) %!d(string=hai) anos | |
| RealtimePlugin.php | %!s(int64=9) %!d(string=hai) anos | |
README
As of StatusNet 1.0.x, actual formatting of the notices is done server-side,
loaded by AJAX after the real-time notification comes in. This has the drawback
that we may make extra HTTP requests and delay incoming notices a little, but
means that formatting and internationalization is consistent.
== TODO ==
* Update mark behaviour (on notice send)
* Pause, Send a notice ~ should not update counter
* Pause ~ retain up to 50-100 most recent notices
* Make it work for Conversation page (perhaps a little tricky)
* IE is updating the counter in document title all the time (Not sure if this
is still an issue)
* Reconsider the timestamp approach
loaded by AJAX after the real-time notification comes in. This has the drawback
that we may make extra HTTP requests and delay incoming notices a little, but
means that formatting and internationalization is consistent.
== TODO ==
* Update mark behaviour (on notice send)
* Pause, Send a notice ~ should not update counter
* Pause ~ retain up to 50-100 most recent notices
* Make it work for Conversation page (perhaps a little tricky)
* IE is updating the counter in document title all the time (Not sure if this
is still an issue)
* Reconsider the timestamp approach