It will be nice because comments can be managed with an external module.

If I have a module (Entity Wall) that can implement a nice comment system in entities. We can easily have walls (like facebook walls) related to an entity. If the logs are entities it will be very easy to add a comment system that is related to the content a log is related to.

It is possible to relate the node comments with heartbeat comments, but better if we can relate to entity comments or just turn off the comments in the heartbeat template and let some entity comment system to do the work. I think in future situations that we can use the D7 Entity properties and funcionality directly aplied to the log entry.

It is possible?? What you think about this?

Comments

Stalski’s picture

Stalski CreditAttribution: Stalski commented
Status: Active » Closed (won't fix)

I can only say that when D7 came out and I started rewriting heartbeat, I was very annoyed to see the comment module still being attached to the node entity. That's the reason why heartbeat uses custom comments OR the core comment module if you configure heartbeat that way.

An activity message in heartbeat is an entity with a heartbeat template bundle. You could add fields to it (typically for the "wall" feature, called ActivityStatus) but in most cases messages will be displayed as a derived extra field which heartbeat builds.

The comments will not be entities, but it would be very easy to add another way of commenting in heartbeat (with some heartbeat changes I persume).
That said, I must say I will not deal with this in D7 at it would overcomplicate things and I think it is already difficult enough for most people to understand how heartbeat works, no offense.

I am not against a proposition (with patch for heartbeat to add the configuration or something, cant be hard) of a contribution that does that job, but it won't be heartbeat itself.