About two months ago, I started a project to have the summary of all absorb effects on a target in Grid. After living a while as a daemon-like addon, I converted it now to an embeddable library. The library is actually a framework on which all spell are implemented upon.
It is able to track all absorb effects currently ingame (player spells that is, see list of supported spells) on all targets around you, including aoe effects like Anti-Magic Zone. The accuracy depends on how many information is available for that specific player and spell, as well as things like party/raid standing. The library communicates with itself to get informations like spell power and talents from other users of this library.
I wrote two addons that implement the library already to show the absorb values: Shield Frames (displays absorb effects with groupable/sortable bars, heavy under development) and GridStatusAbsorbsMonitor
I consider the public API not stable at the moment, so please feel free to express any feedback about it.
Cataclysm and Absorbs
Since the 4.0 client informs us about the exact absorb values on some of the most important spells (but note, not all spells so far: Divine Aegis missing to name the most important), this will greatly increase the accuracy of the library as well as make it possible to get rid of a lot of communication and guessing. I will therefore not make any stable release before Cataclysm.
While we're at it: Power Word: Barrier appears to use a different implementation that Anti-Magic Zone, making it impossible to implement it in the library at the moment (in detail: While it summons a unit to radiate the shield effect like AMZ does, there are no AURA_APPLIED/REMOVED events for players being affected). I alraedy filed this as a bug in the PTR, but maybe someone with beta access is able to raise this as well.
It may just be be me, and it probably doesn't matter, but I would start the name with "Lib", thus it would be LibAbsorbsMonitor-1.0. This is just to follow convention, and in the .toc, under the ## Name: Lib: AbsorbsMonitor-1.0
Thats indeed true. Changing your project into a library afterwards is very sneaky, however we do have some standards for libraries on WoWAce, and we would prefer if you adhere to them.
That is:
- project slug "libabsorbsmonitor-1-0"
- project name "LibAbsorbsMonitor-1.0"
- TOC Title "Lib: AbsorbsMonitor-1.0"
Unless you strongly object, i'll rename the project later, when you had a chance to actually read this message. ;)
There is also a rule about having documentation, and general usefullness of your library, but at least those seem to be fullfilled, imho.
Well sure, I posted it since I think the core is stable enough to be tested and the API to be stabilized, naming issues are always trivial to solve. I wasn't sure it's necessary seeing libraries like CallbackHandler. When you change the slug, are you able to remove the last remaining "default" image please, since it no longer applies to the library itself?
I considered the late change to a library acceptable since it was still marked as beta (and only used by my own addons), and in the end, it resulted in a much, much cleaner interface, both internally and public.
I renamed your project, you will need to update your TOC and .pkgmeta (package-as specifically) yourself.
Also remember to update the remote in your local git repository.
For the image .. well, it appears it is flagged as deleted, however the page insists on using it as the default image.
You can PM ckknight or Kaelten on the page, and they can forcefully remove it from the database if it bugs you.
And yeah, CallbackHandler is somewhat of an exception, because from a user standpoint, we don't see it as a true library, because its supposed to always be embedded in other libraries or addons, and don't live standalone.
No good rule without its exception ;)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Documentation: http://www.wowace.com/addons/absorbsmon/pages/public-api/
About two months ago, I started a project to have the summary of all absorb effects on a target in Grid. After living a while as a daemon-like addon, I converted it now to an embeddable library. The library is actually a framework on which all spell are implemented upon.
It is able to track all absorb effects currently ingame (player spells that is, see list of supported spells) on all targets around you, including aoe effects like Anti-Magic Zone. The accuracy depends on how many information is available for that specific player and spell, as well as things like party/raid standing. The library communicates with itself to get informations like spell power and talents from other users of this library.
I wrote two addons that implement the library already to show the absorb values: Shield Frames (displays absorb effects with groupable/sortable bars, heavy under development) and GridStatusAbsorbsMonitor
I consider the public API not stable at the moment, so please feel free to express any feedback about it.
Cataclysm and Absorbs
Since the 4.0 client informs us about the exact absorb values on some of the most important spells (but note, not all spells so far: Divine Aegis missing to name the most important), this will greatly increase the accuracy of the library as well as make it possible to get rid of a lot of communication and guessing. I will therefore not make any stable release before Cataclysm.
While we're at it: Power Word: Barrier appears to use a different implementation that Anti-Magic Zone, making it impossible to implement it in the library at the moment (in detail: While it summons a unit to radiate the shield effect like AMZ does, there are no AURA_APPLIED/REMOVED events for players being affected). I alraedy filed this as a bug in the PTR, but maybe someone with beta access is able to raise this as well.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorThat is:
- project slug "libabsorbsmonitor-1-0"
- project name "LibAbsorbsMonitor-1.0"
- TOC Title "Lib: AbsorbsMonitor-1.0"
Unless you strongly object, i'll rename the project later, when you had a chance to actually read this message. ;)
There is also a rule about having documentation, and general usefullness of your library, but at least those seem to be fullfilled, imho.
I considered the late change to a library acceptable since it was still marked as beta (and only used by my own addons), and in the end, it resulted in a much, much cleaner interface, both internally and public.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorAlso remember to update the remote in your local git repository.
For the image .. well, it appears it is flagged as deleted, however the page insists on using it as the default image.
You can PM ckknight or Kaelten on the page, and they can forcefully remove it from the database if it bugs you.
And yeah, CallbackHandler is somewhat of an exception, because from a user standpoint, we don't see it as a true library, because its supposed to always be embedded in other libraries or addons, and don't live standalone.
No good rule without its exception ;)