[buddypress-trac] [BuddyPress Trac] #5644: Activity Favorites: alternative management & new features

[buddypress-trac]

#5644: Activity Favorites: alternative management & new features
-----------------------------------+------------------
 Reporter:  imath                  |       Owner:
     Type:  enhancement            |      Status:  new
 Priority:  normal                 |   Milestone:  2.2
Component:  Activity               |     Version:  2.0
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch 2nd-opinion  |
-----------------------------------+------------------

Comment (by johnjamesjacoby):

 My thoughts:

 * “Bookmark” is still a poor word choice. It's already used by browsers to
 imply “Favorite Sites”; it's not modern sounding; it conveys the
 infrequent adding & removing of items, which as a feature makes it sound
 less powerful than it is.
 * As a UI, core default needs to be incredibly simple. No JS, no fancy
 show/hide CSS. Enough markup to make fancying them up possible. We can
 ship with an example of how to extend the UI, but let's not spend too much
 time on what a bunch of avatars in a row looks like.
 * There should exist echo/return functions to individually get: avatars,
 profile links, display names as titles, the total count of likers, and the
 like/unlike buttons.
 * I'd love it if the markup for outputting avatars was a template part, so
 it could be easily overridden in a child theme.
 * Lets ditch the on/off UI, as there's no way to guarantee it applies
 (other than using theme_supports functions, which I would rather not do.)
 Example: In making a child theme that does not support automatically
 refreshing Activity Streams, end users are still left with a visible
 option that does nothing.
 * Re: data storage, I see a few viable options. 1) New database table to
 point the relevant object ID's together. This gives us things like
 timestamps, maybe custom-like-types, etc… 2) Use the activity stream
 table, with a custom action type. We get a lot for free this way. 3) Store
 the same meta_key `bp_user_like` with a value of the user ID, and then
 easily query for and slurp them up for each activity stream object. We get
 less data about each like, but it's simple and fast.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/5644#comment:34>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac