Trigger event when filter replaces content

[CodeMonkeyBanana]

I am using isotope.js for organising members. I added this event so I could trigger isotope code without modifying core. Figured it might be helpful if buddypress triggered some events when it replaces content so you can write javascript that interacts with it without overriding buddypress core js file.

[CodeMonkeyBanana]

custom event trigger

[CodeMonkeyBanana]

Uses promise otherwise fires too early

[CodeMonkeyBanana]

Ignore first file, that one fires too early.

[DJPaul]

This sort of thing is one of the many enhancements that we want to do to that JS file. We have been talking about improving/updating that file for a while now, and I'd probably suggest we wait for that so we don't give ourselves any future compatibility concerns (i.e. we add some now, but we rewrite it all later, and remove some then unnecessary custom events (which people might have started to rely on)).

Conversly, if we did move ahead with something like this in the short term, I'd want to see these added throughout the entire file where appropriate, not just on a couple of lines.

[boonebgorges]

Conversly, if we did move ahead with something like this in the short term, I'd want to see these added throughout the entire file where appropriate, not just on a couple of lines.

This seems like the right way forward in the short run. Let's try to get these in place wherever BP returns content via AJAX, and let's come up with a good naming convention for distinguishing between them. Passing 'object' and 'filter' won't be specific enough (or even applicable) in all cases.

[DJPaul]

Closing most tickets related to BP-Default and BP-Legacy, since the upcoming BP-Nouveau template pack (planned for 3.0) will make these redundant.

[DJPaul]

Closing most tickets related to BP-Default and BP-Legacy, since the upcoming BP-Nouveau template pack (planned for 3.0) will make these redundant.