gnu-social/plugins/Realtime
Mikael Nordfeldth 861e838add pkeyGet is now static and more similar to getKV
Memcached_DataObject now defines
   * pkeyGetClass to avoid collision with Managed_DataObject pkeyGet
   * getClassKV to avoid collision with Managed_DataObject getKV
2013-08-18 15:42:51 +02:00
..
locale Localisation updates from http://translatewiki.net. 2012-06-30 11:10:38 +00:00
cleanupchannels.php The overloaded DB_DataObject function staticGet is now called getKV 2013-08-18 13:13:56 +02:00
closechannel.php The overloaded DB_DataObject function staticGet is now called getKV 2013-08-18 13:13:56 +02:00
keepalivechannel.php The overloaded DB_DataObject function staticGet is now called getKV 2013-08-18 13:13:56 +02:00
Makefile Makefile for Realtime's min.js 2011-03-01 15:33:10 -08:00
README Realtime plugin: fix i18n, thumbnails, location display, OStatus server display, micro-apps display. 2011-03-14 13:29:35 -07:00
Realtime_channel.php pkeyGet is now static and more similar to getKV 2013-08-18 15:42:51 +02:00
RealtimePlugin.php The overloaded DB_DataObject function staticGet is now called getKV 2013-08-18 13:13:56 +02:00
realtimeupdate.css de-IDifying labels in notice form to fix issue with geo pin activating the wrong place when cloning the form 2011-03-08 12:14:44 -08:00
realtimeupdate.js Whitespace updates (including leading tabs to spaces). 2011-08-19 17:06:03 +02:00
realtimeupdate.min.js JavaScript and other changes to make realtime_channel management work 2011-07-13 16:10:08 -04:00

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