Authors CurseForge

I'd like to see addons sending current heals (aka heals that have been started but not landed yet) via a shared library. Squishy could use it, HealWatch/HealSync could, even various unit frames could display the data (e.g. color the unit name green when someone is currently casting a heal on that target).

My proposal: a library that would use:
- AceComm for sending data
- SpellStatus to parse outgoing heals (if only this lib would add target data)

the library itself will do the following:
- send current heals (sender, target, estimated time to land, spellname, spellrank [maybe also healamount once we have a library that can parse the spellbook, gear, talents, buffs and debuffs])
- store incoming data from other players in a table
- fire an event for each heal

I was hoping that HealSync would develop into a library that does all that - but it's not a library, and also contains UI code. Also, its not ace'd - which has pro's and con's (I'd prefer the Ace version though).

Now my question to you guys: would anyone actually use such a library? Or is Squishy the only addon that needs such functionality? Such a library can only be a success if many people are using it.

I'm all for it. That said, I'd like to see some discussion on the actual fomat of the library (data storage and interfacing) so that we can make it as good as possible :)

Will I use it? I'm not sure. HealWatch is close to a 1.0 release so I doubt it'll be in there. But maybe HealWatch 2.0 will use it...time will tell :)

something I've thought about is making this a more generic library that watches for all spells. send all spell cast information (for spells with a cast time or channeled) then have the addons register for only certain spells. this'll open the library to be used by more mods, something like Arcane Party Bars.

just a thought

Josh, I'm a bit unsure - do we really want to have 40ppl in a raid all send each casted spell via the comm channel? Would be a lot of data to parse (approx 15 spells / second).

so what I propose is something where the addon registers what spells it wants to know about back to the library, along with a call back function. something like:

myAddon:RegisterWithLib({<spells>},myAddon:ParseStuff)

myAddon:ParseStuff = function(event,spellName,target,time,[rank])?

i dunno, I'm just throwing ideas out there. The biggest stumbling block for me is always the API.