Activity Stream Comments Block for Solid

Edit PEOPLE, THREADS and the two event lists, FIRST and EARLIER. An event has an id, the person, a kind (commented, replied, reacted, edited, resolved or mentioned), an ISO at, a few words of text and its thread. Groups, counts and the sentence under the stream are worked out from those lists, ordered with the most recently active thread first.

It is pressed while that person's events are shown. Turn it off and their events leave every group; a thread with no events left disappears, and if everyone is off the region says so in the same space. The count on each toggle is how many events that person has among the loaded ones, so it grows when you load earlier events.

No. The events are typed sample data and the block says so. Nothing refreshes, polls or connects. To make it real, load a page of events from your server, group them by thread, and have Load earlier fetch the next page by cursor; keep the person filter on the client for small sets or send it with the request for large ones.

Which people are shown, which groups are open, and whether the earlier events were loaded. Nothing is saved. A real activity stream usually saves the open groups per person only if it helps, and always loads the events from the server.

The people are a labelled list of toggles that report their pressed state, and each group's trigger announces whether it is open. The scroll region is reachable with Tab. Every event says its kind in words as well as with a glyph, and a polite status line reports each change, including the new totals.

The people band becomes a row that scrolls sideways, each toggle keeping its name and count. The groups and events stack in the held region, and the times stay at the end of each line.