I just wanted to clarify about the Incomming Health/Heals stuff:
I am currently using the ExtraBar feature which adds a shaded bar behind the Healthbar with the expected incoming Health. This makes it easier for me to distinguish if a HoT, Lower Heal or Greater Heal is needed (if there is time for the later).
I think the different features people use are:
Incomming Heal Indicator (someone else is Healing the Target)
Incomming Heal Text '+X'(Someone is Healing the Target for amount X)
Incomming Heal Text '+X/+Y'(Someone is Healing the Target for amount X, Your for amount Y)
Incomming Heal Bar %X (The incomming Heal would Heal the target to %X health)
Incomming Heal Bar %X/%Y (The incomming Heal would Heal the target to %X health and your heal up to %Y)
Part of all indicators are the time they require to Cast (e.g. Flash Heal vs Greater Heal) - where the tank might be healed for enough, but the Greater Heal does not complete before the tanks death.
Show the Total amount healed, or just the ticks in the next 2/4/6 seconds ?
The Healthbar is useful as a greater Heal for 5K heals the poor mage with 8k usually to full health, where a well beaten Druid with 25K can take a few.
well, SpecialEvents-Aura provides the basic stuff. I don't think we need any comm-library, afaik the API allows to check the remaining time of all buffs you applied yourself (please correct me if I'm wrong), and I think Grid doesn't really need to care about the time left on hots you didn't cast yourself. xbeeps, if for some reason you want to write a hot library, I'd suggest to make it standalone and not part of LibHealComm-3. But maybe I'm missing a good reason why hots need an inter-client communication.
Oh yes, sorry i forgot only the caster is interested in the HoT's. Still the outgoing ticks should be sent to libhealcom (e.g. 3Stack lifeboom in 2 secs - lifebloom full heal in 4 secs (and this one should update / be delayed if lifebloom is renewed).
I would object to both these requests. The first because this is information clutter that I don't need/want to be able to heal effectively. The second is because you would be missing completely the whole point of Grid, which is to have all unit frames closely together to be able to see and respond as fast as possible to any damage that is received by the raid.
I can see your point in that and the small size of Grid was the reason i chose it. With the introduction of Petframes i would like to use them, but somewhere else, and if possible i would like to change their location within the game sometime in the future (atm they keep growing into my target and targetoftarget frames).
While in combat you are right, i am not interested in seeing who is Master Looter or similar, but out of combat this is still interesting to me, like Grid won't show missing Buffs in combat by default.
I would like to see Maia's vision of some 4 submodules (Healing, Debuff, Extra-information ...).
New modules could be created like they are now, and after they have proved they are stable become integrated in the above named sub categories.
New indicators like a gradient (a Dot changing color based on a duration, the Healthbar changing the color based upon Health left (ration and/or absolute - E.g. when a boss hits for 5K randomly a bar below 5K turns red), blinking and a small (3-5 px line) bar to indicate HoT durations would be nice new features.
So the configuration profiles, i would put the 'Grid' (location of the Grid, and layout of the unit-frames) in one category (maybe different profiles based on raid size 10, 25, 40 or location Battleground vs PvE). The configuration of Indicators in another one, that defaults to Class.
E.g. if i change the layout of my Mage and i want to use it on my priest, i need to repeat all the steps i did on my Mage again, or copy the profile and adjust all my indicators, custom Buffs(Inner Fire, Weakening Touch, Prayer of Mending). I hope i just missed a better way and there is an easier way to do this.
Looking at the members of my guild with average users, i think the way Grid is too complicated for most. Maybe they are not the intended User-base coming back to my Unix quote.
So for the time being i would add to Raid Leader and Healer the word 'Power User'.
Quote from maia »
4) UNIT STATUS: either displayed as text or as corner indicator (oh, if we'd have tooltips they'd be useful here too), showing basics (pvp status, offline, >100 yrds away, ready,...) but maybe also the results of oRA queries (e.g. durability)
I would like to add 'Master Looter', 'Raid Assistant' and 'Raid Leader'. The only reason i still have Pittbull Raid Frames around.
As for the layout code, I think we can reduce the options too, we only need some basic settings like "sort by group or class", "display pets?", "display all raid units or limit to max number in instance?" and Grid will do the rest.
I would like to place the pets somewhere else. Or be able to place some Raid groups on a different part of the screen (or redesign my setup again). Currently they grow into my target and TargetOfTarget frame which is a bit messy.
Maybe a default 'reduced' configuration with reduced options and an 'enable expert options' check box which does unlock additional configuration features.
For user base don't forget the debuff curing. I have a detox/decursive status module in the works, but I might hold off releasing it depending on Grid-Ace3 schedule and feature changes.
Wait, I am not an author of Grid. But i wanted to point out a few things i see that could be improved and some i think will need a major change of the API and would break most existing modules. Grid grown up for more than 1 year and maybe the changes and needs could reflect a major change.
maia mentioned there might be a next major version of Grid
Quote from maia »
Pastamancer has been thinking about such a feature for a next major version of Grid, including an optimized configuration. There's no schedule for it yet.
I wanted to start a scetch of which features it should have (core or modules).
I think the information presented in Grid is mainly needed by Healers and Raid leaders. A tank or a damage dealer usually just needs a debuff indicator. So the design should focus on the needs of theses 2 classes.
For me Grid's strength is:
Stability: there is little fussing with the code - the modules API is stable (as modules written more than 90 days ago still work with it.
good Information / Area ratio Grid is able to concentrate a lot of information on a small area
Interaction Unitframe based addons e.g. Clique, Click2Cast
For me has a weakness in:
High Learning Curve: Grid is hardly intuitive, but rather a Unix OS with it's manual scattered in the world wide web.
High amount of modularity: just counting my 20 Grid 'main' addons maintaining these without WAU seems a nightmare to me, and i can hardly convince an 'average' user to install it.
Hard to configure The high amount of flexibility and it's growth in extensions has made configuration become complicated.
Synced Healing: This only belongs to a subset of the Grid Users, but still synchronized healing is spread into lots of different standards.
A new version of Grid should from my point of view focus on Raid Leaders and Healers. Be aware and keep it's strengths while working on resolving it's weaknesses.
I hope i don't forget any.
Layout import / Export feature: Currently it is very complicated to share a successfull layout with another person having Grid. (-> Post cool PitBull layouts here!)
Settings To reduce the learning curve i think Grid should ship with a usable class default for each available class (show Missing Buffs - Magic / Desease debuffs for Priests, MoTW - Curse / Poison for Druids). Furthermore the configuration should differ between layout, that can / may share across characters and the status display, that most likely will differ between each class.
Rewrite the current Status display. The current configuration is not aware if the status can actually be displayed, and makes it possible for a Spell Indicator to be mapped to a health bar and thus fail to be visible.
Status Class Each Status is also a class. So a Corner Indicator cannot be assigned to a Health bar
Bar(Health, Mana, Rage, Energy) - Displays a numerical value mapped to a bar with a color and a priority - Bars can Stack (e.g. Incoming Health behind current Health)
Icon - Can be any icon (Master Looter, Raid Leader, Raid Icon, Spell, ...) with a priority
Indicator - shows a geometric form (e.g. square) in color
Text - Shows a Text with Color
Status creator An Status creator can implement any number of Status classes.
E.g. UnitHealth can implement a Bar with the current Health, a Text with it's numerical value
A Spell (PW:Shield) could implement an Icon (spell Icon) and an Indicator (yellow square)
Lifebloom could export an Indicator with Lifebloomstacks, Lifebloom duration, A Text with the duration and maybe a Bar for the lifebloom duration.
Party/Raid Layout: as far as i know this has to be edited outside of the game. a Feature to sort them in-game (maybe with a dummy raid feature simulating a 40 man raid - so you don't have to enter AV just to setup grid) would be nice
Unit Frame Layout This would display a normal and an over sized single Unit Frame (the smaller to show the actual display, the larget to make the configuration easier). A user could assign how many bars he wants to have - the number and location of text indicators etc.
Indicators to Unit Frame Layout Again a normal and an over sized single Unit Frame. Hovering over an Status class will make it light up. Clicking it will show a list of list of available Status that match the currently selected Status Class.
If no Status class is selected the whole Status list is shown. Clicking a status will light up the corresponding selected Status classes (thus make it possible to find if it is bound and where).
synchronized Healing core module as stated above, i belief a lot of Grid users are healers. Implementing a healing Library that can be extended to 'speak' with other healing libs or choosing an existing one would help a lot
Quote from maia »
It seems as if xbeeps is trying to make LibHealComm-3 a complete package that does all anyone will ever need. If that's the case, I'd suggest to replace the default GridStatusHeals (and CastComm) by a new GridStatusHeals using LibHealComm-3 and add in the additional functionality of the GridStatusIncomingHealth, GridStatusHotStack. Ideally, if neither of the indicators are bound to display any kind of heals (and the user doesn't play a healing class), the code would disable itself and not cause additional CPU/memory overhead. And while I usually prefer optional modules, I consider this feature so important (as I assume 90% of the people using Grid are healers or raid leaders) to move it into the core.
As always, if anyone is volunteering to do the above, please branch Grid, implement the changes, give the community a week or two to test, and hopefully by then we also have a final LibHealComm-3 version we can use.
insert class buffs: The current grid version is unaware of lots of buffs. For example:
Priests: Inner Fire (Self, Class:Priest, Show if Missing), Weakening Touch (Race: Bloodelf, Self, Class:Priest, Show if Missing)