- Changed functionality so messages are fetched by number of records and not by timestamp.
- Added pager property to info so the messagebuilder knows more on how it should display things.
- Added a per-message  property to overrule the maximum number of messages to merge together. The
  global setting is overruled if the message specific one is set. For instance, when uploading images,
  layout-wise we want to show 5 images in the summary. But if pages are the context of activity, then i
  will only show 3 of them.
- TODO Make the pager ajax compatible and add settings for each access type

Refactored the code for access type objects. Very simple now to use them. Tests seem to have changed nothing on results, which is good

adding settings to configure the displays

Changed the logic to merge messages together when there are more users involved. UI wise a new setting is thrown in at the administer message edit and add form

Each heartbeat activity row can have n- attachments. Such as flags and now the comment. You can react and show reactions on the message.
Enjoy

Added a default message and default rule in case image module exists. I added a token of course to substitute that part in the messages.

Removed code for module and message_type properties of a message. Tags were introduced so ship this :)

An autocomplete field will have us categorize our messages to more specific activity streams.
Now i plan to remove the older things that ment for this (module, message_type) have become unnecessary

Changed the insert and update and delete functions to more atomic parts so they would be usable to other contribs

Added flags integration as POC
Separated views completely from base heartbeat module to have heartbeat fungate as an API instead of a utitlity module

- views module filter depending on choice of message-module
- whoisuser filter for views, making it possible to use path based uid (user/uid for example)

- views update to the access handler, taking a extra filter argument acting user/requested user
- extra default block provided to show on the user /profile page

by clearing the rules cache

Merging is fixed for views aswell. Be carefull, stay with the heartbeat_row style plugin when making your own custom views

The grouping of messages is fixed now
I found a big error in my code while storing the relations of a user. Fixed.
The public and private heartbeat have been altered due to a big change in code. A peer review indicated that refraction was needed. The sollution we came up with is a message builder as context of a state pattern. The concrete state objects are derived from a base heartbeat access object performing certain taks for all states. Little implementation of a template method pattern.
Furtheron the heartbeat stores its info about relations. (init hook used to store data to the heartbeat_relations in the global user object). This info can easily be retrieved from a heartbeat instance.