Content display

The module is now obsolete. New frameworks such as comet or HTML5's websockets should be used instead.

Live Update is a module that provides a flexible and scalable to provide up to date in content to users without requiring page refreshes. Live Update uses JQuery to poll lightweight text files that tell the users' browser if new content is available. If so, JQuery then makes another call to get the updated content stored as static HTML.

A blog post detailing how one might use this API to set up a Question and Answer (similar to our PBS Engage work) scenerio is here

API

Live Update provides a simple API for modules hook into and allow Drupal to store, retrieve and insert content updates of all kinds. The API breaks down into two basic functions:

Telling the browser how and where to look for updates and what do to when you found them.

live_update_initialize($element, $settings)

Telling Drupal to record a new content update.

live_update_update_content($element, $html, $settings)

Live Update Modules

This module provides Live Update functionality for:

This is an implementation of the UMapper.com API allowing for easy creation and addition of maps to your nodes. You can choose from the following mapping providers:

This module creates an easy live blogging feature to provide live coverage of an event. The content administrator can create a live event node and add updates to that node.

IMPORTANT:This module is temporarily abandoned in favor of Browsing History Recommender module. Please refer to #509858: migrating to Browsing History Recommender. Future release of the module would take user relations from social networking modules and then make the user-to-user recommendation.

----

The basic idea of this module is to automatically find similar users in the community, and then recommend new contents to users based on the fact that other similar users liked the contents. This is actually an implementation of collaborative filtering used in many recommender systems.

To calculate similarity among users, we now only adopts the user-comment relationship. That is, if two users made comments to the same nodes for several times, then we consider them quite similar to each other. This is especially useful for communities that have forums enabled. There might be other approaches that calculate similarities between users, but I haven't thought about it thoroughly. You are welcome to submit your ideas to the issue queue.

Allows admins to hide workflow comments based on the state of a node in a role-sensitive way.

Homebox allows site administrators to create dashboards for their users, using blocks as widgets. Blocks in a Homebox page are resizeable, and reorderable by dragging.