More and more, drupal site builders have to make choices that they shouldn’t if it comes to “choosing which contrib to use”. We often can choose for an API - which is great - or choose for a ready-to-go module. As a developer, I will choose most of the time for the API. The problem here is that several API’s are available.
This weekend, i felt like writing something totally redundant but from a nostalgic and funny point of view. Taking this site as example, you wrap your site into the pacman container.
This evening, I uploaded a downloads section at the heartbeat demo site. The modules the site is created with, are downloadable from the site.
Heartbeat is an API that allows logging activity messages to the database. These logged messages are listed up to form a heartbeat stream. There are three built-in streams but developers can register their own. How these messages are getting logged, is fully up to you. Programmers can call the api function for events based on custom criteria. Non-developers and themers can enable the submodule heartbeat_rules so they can trigger events for heartbeat to log the activity. The powerfull module it depends on is rules.
This page holds links to documentation about the module “heartbeat” for drupal 6. From here you will find how to install the module, how to use it and how to implement its hooks. As many drupal contributes, heartbeat comes with an export for messages that can be pasted in a hook function.
Heartbeat highly depends on the rules module. Rules allows other modules to describe default rules, and that’s what heartbeat does. The messages you build are exportable into default as well.