• 0

    posted a message on oRa heal parsing module / HealSync / comm standard
    Quote from dafire »

    I think a mod should only broadcast own casts to prevent unnecessary spam.


    I'd agree.

    As far as the library goes, someone should look into IsCasting by AnduinLothar (here WoWI).
    Add some way to filter the spells and a communications portion and I think that gets it started nicely.

    I think it should be up to the individual mods as far as the format for storing the data is concerned. While I'm sure we could come to some agreement on a format, is it really necessary when we could call functions with the paramenters passed to the function.

    Just my 0.02
    Posted in: Addon Ideas
  • 0

    posted a message on oRa heal parsing module / HealSync / comm standard
    Hi maia :)

    I think whatever this thing is, it should be an embeddable library that handles parsing spell casts (like AnduinLothar is doing with IsCasting) and has an optional component to watch the spell cast notifications.

    IE: Your addon can use the mod to watch for spellcasts and broadcast them and/or listen for broadcasted spellcasts. Why both options? Warriors don't have many spellcasts they need to broadcast but it would be nice to see what heals are incoming, same goes for rogues or mages or warlocks (yes I know there are bandages etc etc).

    It should be in the same library so that the data format is standardized.

    As far as the format is concerned, in HealWatch I am using a hash type setup. When I release my next version, the message format is something like: <command><spell index><time><target> with <command>,<spell index> being 1 character each, time being %.3f and target being a string. This was the smallest I could think to make the message so it sends the least amount of data. Now, I'm not saying it's the best format, it's just the one I'm using (not that I ever got communications working ;)).

    Now as far as watching for events, the so called back-end of HealWatch, HealSync, etc, I think more discussion should be placed on it. I don't like the way HealSync does it because it scans the raid every time it needs to determine the target. I would rather it keep a table of what name corresponds to what raid index.

    For me, it seems the way I would use a library like this is to register my mod for with the library and give it a table or list of spells that I would like to be notified about. Then when a spell I'm watching, say Flash Heal is cast, the library passes to my addon (through some call-back function) either a table or a list of arguments that contains all the information it has about the spell. IE, if I cast Flash Heal then the library passes my function the spellcaster, target, spell name, cast time, optionally? the spell rank, optionally? the estimated damage/heal. My function then calls the libraries function to broadcast that information, if I want it to.

    If the library sees someone else cast Flash Heal, then it passes my addon the spell caster, the predicted target, spell name, and estimated cast time. Now what if we are both using communications? How do we handle seeing the CHAT_MSG_SPELL_FRIENDLYPLAYER_BUFF and the addon communication message? We want to give precedent to the communicated information since it will be more precise.

    Just some things to think about :).

    BTW, the library should use HealSync's time estimation, for both spell casts and for spell landings (using latency etc).

    So I guess those are my thoughts on the matter.
    Posted in: Addon Ideas
  • 0

    posted a message on Squishy 0.10 [2006/08/22]
    i'm sure maia would be more than happy to implement something like it if you presented him with a patch that does just that :)
    Posted in: General AddOns
  • 0

    posted a message on Clique 0.2.0-Beta Released
    is there any duplicate checking as far as click combinations are concerned? I think I was able to bind ctrl+alt+left button to 2 items. In the clique menu it showed up as one being ctrl+alt+left button and the other alt+ctrl+left button.
    Posted in: General AddOns
  • 0

    posted a message on FuXPFu - (As inspired by Bant)
    no option to have just the rep bar show when fubar hides? ^_^
    Posted in: FuBar AddOns
  • 0

    posted a message on Squishy 0.10 [2006/08/22]
    Quote from maia »

    JoshBorke, I guess I just added CastParty support to Squishy, please give it a try. If it doesnt work, take a look at lines 87-88 and 431-454 in core.lua.


    works :_) thanks :-) don't know how i missed those later lines...
    Posted in: General AddOns
  • 0

    posted a message on Squishy 0.10 [2006/08/22]
    can anyone confirm if click casting is currently working in Squishy? I see a SquishyCustomOnClick, but I can't find where it's used...

    (I want to add in CastParty support :-P. I just love the bars in castparty)
    Posted in: General AddOns
  • 0

    posted a message on Squishy 0.10 [2006/08/22]
    Quote from maia »

    Okay, so basically we're talking about four core routines, most of them can be embeddable libraries (dependencies are so 2005!), plus an addon of choice:

    1) a library that does basic channel stuff - joining, leaving, providing an api. In my personal view, it should somehow integrate with CTRA/oRa. Altering the oRa core code to use that embedded library should be simple (or maybe oRa-core should contain this functionality itself), and I guess haste might not have a problem with someone adding an API to oRa as long as it's a working, non-messy code.

    I like the way that CTRA does channel management and I think any other library should have that same functionality. That means that it will have to create the frames or commands to control the channel. ALso some way to control who sets the channel.

    Quote from maia »

    3) a library that hooks spells being cast (basically Squishy/hooks.lua = oRA_Resurrection.lua = CT_RADetectSpells.lua), watches for SPELLCAST_START, _STOP, _DELAYED events, makes that information available to other addons (maybe via a SPECIAL_EVENT?).

    would this include target detection? IE the library sends the spell, target, and status

    Quote from maia »

    4) a library that will send outgoing heal (watched by the hook, containing heal amount,...) in a unified way (probably something like: SpellID#Rank#HealAmount#ETA#TargetName#start/delay/cancel). Also this library should be able to parse incoming data (both via the channel defined by library 1, see above) and make it available (firing a special event or any other API).

    should ETA include delay time or would that be part of the addon that registers? I think that the start/delay/cancel should be some index value, but of course that's obvious :-)

    Quote from maia »

    Finally, addons of our choice (Squishy, HealWatch,... but maybe also PerfectRaid, WatchDog, XRaid, MiniGroup etc) could use that data. All they need to do is drop the above four libraries into their addon folder. I guess if oRa on the one hand, heal trackers like HealWatch on the other and raid addons on the third side all contain these libraries, chances are rather large that we're talking about setting a standard here which probably even CTRA might integrate sooner or later - but even if not, one could still provide a small addon that basically only contains the libraries without and display logic and ask healers in your raid to install it.

    PS: sooner or later we should stop hijacking my addon thread and move to the developers corner. :)

    i agree, where's the new thread?
    Posted in: General AddOns
  • 0

    posted a message on Squishy 0.10 [2006/08/22]
    In HealWatch I'm just hooking into CTRA's communication commands. I don't do any of the stuff myself except parse the messages I generate.

    I would be more than willing to convert to a common API and a common channel setup. It was something I was considering for HealWatch. The idea to be able to use Sky, commChannel or CTRA or any other mod that someone wrote an interface for. Alas, I do not have the skill to do that properly :)

    Onto the more specific problems I see with a comChannel addon is scope. Sky already has it's own communication channels it sets up. I feel we need to strive to not use up all the channels with addons. But of course I don't know how to do that. :)

    With regards to CommChannel, I personally don't like dependencies. I know there is nothing wrong with them, I just don't like having to package them with my addon. I much prefer embeddable libraries. So, um, yea. I lost track of where I was going.

    Basically, HealWatch is all for a front-end/back-end setup where the back-end is some embeddable library.
    Posted in: General AddOns
  • To post a comment, please or register a new account.