[2008/06/05 23:29:18-154-x1]: Grid2Options\GridIndicators.lua:87: attempt to index global 'media' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:705: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:526>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...de\Libs\AceGUI-3.0\widgets\AceGUIWidget-DropDown.lua:404: in function <...de\Libs\AceGUI-3.0\widgets\AceGUIWidget-DropDown.lua:396>:
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...s\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:328: in function <...s\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:323>:
I just checked out Grid2 and Grid2Options, and get several errors when opening the options:
[2008/06/05 17:38:42-839-x2]: Grid2Options\GridFrame.lua:38: attempt to call method 'ScheduleEvent' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:705: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:526>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:748: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:740>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
Ace3\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:136: in function <...dOns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:125>
[2008/06/05 17:39:42-839-x3]: Grid2Options\GridIndicators.lua:87: attempt to index global 'media' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:705: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:526>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-DropDown.lua:404: in function <...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-DropDown.lua:396>:
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...3\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:328: in function <...3\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:323>:
On initial load, all of the font/texture dropdown selections are blank; I am able to open the dropdown and select a font/texture, but the frame is never updated to reflect this. I formed a raid group for testing purposes; the first frame was displayed with the default Blizzard texture, while subsequent frames were displayed with the Grid gradient texture.
On a more general note, I have a few questions:
1. Will the "blink" behavior be optional? I do not ever want anything on Grid (or any other part of my UI) to blink, flash, shake, or otherwise animate. Astigmatism is annoying enough when viewing static images; while some people with normal vision may find blinking useful to grab their attention, it just makes the blinking object more difficult for me to see, and makes the things around the blinking object more difficult to focus on.
2. Will the "text2" indicator be optional? I prefer to have only a single center text indicator, in the middle of the frame.
I do get similar errors as Midian666 and Phanx when trying to change texture or font, hadn't gotten around to test that before, but all the "important" stuff still works well :)
Picking textures and fonts still not working for me with newest update, but it's still just cosmetics and rest is working fine for me (using it as healer together with clique)
I'll post errors just in case u wan't them.
on initial loading /grid2 i get:
Grid2Options\core.lua:9: attempt to index local 'module' (a nil value)
Grid2Options\GridBlink.lua:3: in main chunk
<in C code>: in function `LoadAddOn'
Grid2-$Rev: 74477 $\GridCore.lua:132: in function `?'
AceConsole-3.0\AceConsole-3.0.lua:59: in function `value'
Interface\FrameXML\ChatFrame.lua:3040: in function `ChatEdit_ParseText':
Interface\FrameXML\ChatFrame.lua:2732: in function `ChatEdit_SendText':
Interface\FrameXML\ChatFrame.lua:2753: in function `ChatEdit_OnEnterPressed':
<string>:"*:OnEnterPressed":1: in function <[string "*:OnEnterPressed"]:1>
---
and trying to change texture:
Grid2Options\GridIndicators.lua:89: attempt to call field 'SetFrameTexture' (a nil value)
Grid2-$Rev: 74477 $\GridFrame.lua:187: in function `WithAllFrames'
Grid2Options\GridIndicators.lua:89: in function <Interface\AddOns\Grid2Options\GridIndicators.lua:86>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:705: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:526>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-DropDown.lua:404: in function <...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-DropDown.lua:396>:
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...3\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:328: in function <...3\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:323>:
But as mentioned main features which i want/need it for works nicely ;)
@Tenelov:
What is the cooldown monitor addon near the center of your screen?
@Jerry:
I've modified my local copy of Grid(1) to allow me to display dispellable debuffs using their cure spell icon rather than the debuff icon. For example, if someone has Wound Poison on them, and I have the Dispel Poison spell, I see the Dispel Poison spell icon instead of the Wound Poison debuff icon. I find that this makes it much faster to recognize what type of debuff it is. The icon border that Pasta added is a nice touch, but it's just not enough. Anyway, I would greatly like to see this feature in Grid2, both because I'd rather not have to keep copying and pasting code every time there's an update, and also because I think it would benefit other people greatly as well. I can send you a diff against Grid if you're interested.
Tenelov, how did you manage to have that layout with Grid2?
I mean, the vertical one?Plus, my guildmates' life isn't showing the same way as yours? Special layout, maybe? Or did I miss something?
Please stop ask about my UI. This topic - Grid2!!!!!
On my screen Grid2 in bottom right part, vertical layout - its my layout Grid (not Grid2).
Froum, look at PM
Well it all looks good so far. Love built in efficient mana bars. My wishlist includes built in support for the following:
* Grouped Buffs. Right now GroupStatusMissingBuffs (badly named) does this. It groups related buffs together, mark + gift of the wild, welfare priest spell + prayer version, welfare blessing + greater blessing. This lets me assign a single indicator to both buffs (they are equivalent) and see who is missing it (show when missing option for buffs). It is ok for this to still need a plugin as so very few spells need it (as long as the show indicator when buff is missing option is standard). However without this ability you just can not use Grid for buffing.
* The side indicators. The 4 that come with grid are just not enough. I am not interrested in how a combination of overlays, blinking lights, cryptic color codes etc. can turn 4 little squares into all the indicator status u could ever need. They can not and do not. (Yes I have posted on this in the grid forum b4 ;-p) As an example, my druid needs to track total hots, both swiftmendable hots from any druid, all 3 hots I cast, including the lifebloom stack.
* Idealy there is just a given set of the "corner" indicators (at least 8, psossibly the 3 per corner ones) and you pick exactly which ones to activate from the setup ui. So if you want to you can have top, top left, top right, bottom left 1 2 & 3, bottom right.
* Same with icons. I would love to have 3 icons side by side, with my curable ones left and right and Raid Debuff in the center. This would eliminate dying due to lack of healing / curing just because some icon obscures another.
* I am keen on seeing the blinking thing used to indicate buff expiry. I am hoping it can blink more rapidly as the buff dies. It would be totaly nice in raid to have long duration buffs start blinking 10 minutes b4 expiry so they can be refreshed for a boss.
* For the settings UI I would kill for a one button switch from everything is dark and dismal to all bars are bright and shiny like regular unit frames. It is just as valid to set up grid that way as "everything is dark except stuff that needs attention". The very first thing I have to tediously walk people through is getting it to have a sane display of health that fits standard interface conventions as seen in bar graphs, stuff on the nightly news, all other unitframes.
* Ok this one is something that is an issue in AutoBar as well: if you have more than one character then the standard Ace profile system is total garbage. It is simply not the case that you set up common stuff, copy it around and never ever change it again. Instead you have a bunch of common settings that you may want to adjust from time to time as you get new plugins or tweak your interface etc. You also have a bunch of class specific settings. For instance, stuff I can cure status 1, 2 and 3 (pallies can cure 3 things I think). Or buffs I can do 1-whatever. Or maybe even character specific nuttiness like my raid leader enables seeing absolutely every buff, debuff, etc. in existence.
Toadkiller, it seems like you want everything Grid isn't supposed to be. I'm strongly convinced you're better off with normal unit frames. Grid is about "reducing to the max".
i atleast think side indicators should be implemented into Grid2. easy to implement, and also easy to turn off for those that don't want them. side indicators are incredibly valuable for tracking buffs. and i could see how having atlest two side by side indicators in each corner could be helpful for some, although i personally don't need that many (i use 5-6 indicators depending on class, 3-4 corners and left and right side).
phanx's idea of using the cure spell icon instead is very nice.
as far as buffing. seems like Grid handles this pretty well to me. it can be set up to show when a buff is not on the target correct (not real sure, showing when the buff is on the target has always worked for me)? other than paladin blessings, which i would not use Grid for anyway, i think it can handle buffs just fine.
i atleast think side indicators should be implemented into Grid2. easy to implement, and also easy to turn off for those that don't want them.
It's not about how easy something can be implemented, and it's also not about being able to turn them off. Grid's concept is minimalistic. If people want additional functionality, they'll need to install additional modules.
It's "opt-in", not "opt-out".
PS: we have to find a naming convention to prevent new users from installing Grid2 with *all* possible modules from the svn.
i know, but i really don't think having side indicators complicates things at all. Grid would still be very minimalistic compared to other party/raid frames side indicators or no. i think it just makes sense to be in the core, but I have no problems using a plugin if needed. mana bars made it in? that's great and all if it's true, just did not expect it. if mana bars are not overkill, how are side indicators?
i know, but i really don't think having side indicators complicates things at all. Grid would still be very minimalistic compared to other party/raid frames side indicators or no. i think it just makes sense to be in the core, but I have no problems using a plugin if needed. mana bars made it in? that's great and all if it's true, just did not expect it. if mana bars are not overkill, how are side indicators?
While not having been in touch with Jerry lately, keep in mind that Grid2 is in heavy development. Nothing you might see in a build or two is set in stone. You might see many things pop up and disappear again, I suppose Jerry is just making sure that optional modules will work correctly. The decision on the final default configuration has not been made, and it won't be made in the next days either.
I strongly disagree with your assessment in that wiki page that Grid is "useless as is" for healers. I've added my comments on the wiki discussion page; I concur with Maia that "regular" unit frames would meet your needs far better than Grid, and will probably rewrite that page to keep it more in line with the developers' concept of Grid, which I feel is more than sufficient for effective healing (with the exception of druid HoT management as noted in my comments).
As for the Grid2 stuff, I hope that the mana bars, no matter how "efficient" they are, are removed from the Grid2 core.
I also do not feel that any of the things listed in Toadkiller's post belong in the Grid2 core. Some may be necessary for certain classes, but class-specific features should stay out of the core. Buff grouping is really only useful for druids, mages, and priests. (Paladin buffs are simply too complex to manage this way and are better suited to a separate addon like PallyPower, although there was an interesting discussion in the PallyPower topic a while ago about a PallyPower Grid plugin.) Fine-grained HoT management is only useful for druids. Toadkiller may feel that 4 indicators are not enough, but I don't even use all 4, and can't think of anyone but druids who would need more than that. Multiple icons, multiple corner indicators, and buff duration tracking are far more clutter than Grid was ever designed for. Please keep Grid2 as basic as possible; if it's extensible via plugins, then there is zero issue with people writing plugins to add 500 icons and 1000 indicators and 12 mana bars, but none of this stuff should bloat up the core pacakage.
Edit: Many errors!
On opening the config:
[2008/06/07 14:59:34-868-x1]: Grid2Options\GridBlink.lua:3: Usage: GetModule(name, silent): 'name' - Cannot find module 'Blink'.
AceAddon-3.0\AceAddon-3.0.lua:144: in function `GetModule'
Grid2Options\GridBlink.lua:3: in main chunk
<in C code>: in function `LoadAddOn'
Grid2-$Rev: 74477 $\GridCore.lua:132: in function `?'
AceConsole-3.0\AceConsole-3.0.lua:59: in function `value'
Interface\FrameXML\ChatFrame.lua:3040: in function `ChatEdit_ParseText':
Interface\FrameXML\ChatFrame.lua:2732: in function `ChatEdit_SendText':
Interface\FrameXML\ChatFrame.lua:2753: in function `ChatEdit_OnEnterPressed':
<string>:"*:OnEnterPressed":1: in function <[string "*:OnEnterPressed"]:1>
[2008/06/07 14:59:34-868-x1]: Grid2Options\GridStatuses.lua:9: attempt to index local 'status' (a nil value)
Grid2Options\GridStatuses.lua:31: in main chunk
<in C code>: in function `LoadAddOn'
Grid2-$Rev: 74477 $\GridCore.lua:132: in function `?'
AceConsole-3.0\AceConsole-3.0.lua:59: in function `value'
Interface\FrameXML\ChatFrame.lua:3040: in function `ChatEdit_ParseText':
Interface\FrameXML\ChatFrame.lua:2732: in function `ChatEdit_SendText':
Interface\FrameXML\ChatFrame.lua:2753: in function `ChatEdit_OnEnterPressed':
<string>:"*:OnEnterPressed":1: in function <[string "*:OnEnterPressed"]:1>
On attempting to change the bar texture:
[2008/06/07 15:00:05-868-x1]: Grid2Options\GridIndicators.lua:88: attempt to call field 'SetFrameTexture' (a nil value)
Grid2-$Rev: 74477 $\GridFrame.lua:187: in function `WithAllFrames'
Grid2Options\GridIndicators.lua:88: in function <Interface\AddOns\Grid2Options\GridIndicators.lua:85>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:705: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:526>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-DropDown.lua:404: in function <...ns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-DropDown.lua:396>:
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...3\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:328: in function <...3\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:323>:
why do i need to learn that 'white' is Missing PW:Fort when there does exist a well known icon for it.
I have no idea why you would need to learn that; the center icon should work fine for missing buffs.
I don't want to use an extra unitframe just to see who is RA/RL/ML, same goes for nearly all other extensions.
As this information has absolutely no bearing on actual gameplay, I don't think it belongs on unitframes at all. If you can't remember who is the master looter, it's fairly straightforward to open the raid panel and check. Grid frames should contain only the information you need to make gameplay decisions, such as who to heal, or who to dispel poison from, or who needs a Blessing of Protection.
It maybe usefull to keep the core small, but maybe ship Grid with some extra packages.
I disagree. I believe that the focus should be on starting people with only the core addon (which would contain only the basics, and no class-specific stuff), and adding plugins only to fill specific needs. This is in contrast to the current system where the norm seems to be to install everything that has "Grid" in its name, and weed out the duplicates/nonfunctional/unnecessary plugins afterward. I also believe that no plugins should be officially endorsed as "mandatory" or "recommended"; there is no single set of plugins that will meet everyone's needs, which is why the plugin architecture exists in the first place. In fact, out of your list of nine plugins, I think five are totally unnecessary and have never used them or wanted their functionality. If you need them to play, then by all means, download and use them, but don't try to push your personal preferences on others. We already have enough issues with new people and plugin overload. Keep the core simple, and keep plugins small and focused.
From my point of view GridIndicatorText3, GridSideIndicators, GridIndicatorSideIcons should not be needed as a separate Addon. If the core comes with a TextIndicator, an IndicatorField and IndicatorIcons it could also be possible to create a new Indicator Location, new TextIndicator location with Tools offered by the Core Itself.
It's simpler both from a development standpoint and a user standpoint to keep indicator modification/creation out of the core, and have new/modified indicators provided by plugins. From my point of view, none of those plugins are remotely necessary for Grid to be an awesome raid healing tool; why should I have to run the code to support them if I will never use them? Again, the plugin architecture was designed for exactly this reason -- if you want extra features such as those you mentioned, it's very easy to install plugins to provide them.
Maybe with the option to import / Export this layout. So people can import the 100-Indicator-300-Textindicator-SuperBigLayout into Grid. Personally i found the layout import/export function very usefull when i started using pitbull. I had a look at the screenshots and took which layout i did like most.
I think Jerry's pretty attached to the idea of in-game layout exporting/importing/sharing, but personally I'd rather not see any of this garbage in the core. Nobody else's Grid configuration can ever be as effective for you as one you create yourself.
I do not get why people are freaking out like this. Jerry clearly stated that he wants the core super minimal and all the complexity in the lod Config. Now the core _could_ demand that you have 4 corner indicators. It could also just have the ability to have 0-n "corner" indicators and you decide how many you want and where. There is really no functional difference between supporting 1-n and supporting exactly 4 and any extras must come from a plugin.
Quote from Phanx »
...Toadkiller may feel that 4 indicators are not enough, but I don't even use all 4.
Exactly, why write the core to force 4 on you if you only use 0, 1, 2 or 3? If you only use 3 why force an asymetric arrangement on the user? Why not let them pick topleft topright & bottom for example? Why not have the ability for the config to allow 1-16 square indicators to be activated? Unless activated the fact that you could have 16 is irrelevant to the user that only uses 2.
Similarly, why only 1 icon? Why not 2 or 3 or even 4? This still lets a user use 0 or just 1, but if they want to they can use more. "reducing to the max" is fine as far as it goes, but at some point you are losing the ability to be effective. Forcing both debuff icons into one icon indicator is just not optimal for me. Sometimes players have multiple debuffs. Sometimes they have boss debuffs on top of that. Shoving that into the same icon leads to wipes or forces me to disable some and so be less effective.
For my mage I want exactly 1 square indicator for buffing, 1 icon for curing stuff, 1 icon for boss debuffs. Thats it, dont care about anything else. Old grid was obese for this. Grid2 sounds like it can be slimmed down closer to what is needed. I hope layout information can be separated from the rest so my tiny mage Grid can still line up on one side with my much larger druid Grid in my overall UI.
Quote from maia »
Toadkiller, it seems like you want everything Grid isn't supposed to be. I'm strongly convinced you're better off with normal unit frames. Grid is about "reducing to the max".
Please lets not be silly. I like grid, I just want provision for more flexible basic features than it comes with. And I cannot stand the default inverse color scheme. As stated I am happy with specific stuff like the combined buffs being in plugins. The druid stuff definitely will be in plugins.
As for my comments about the default grid not being usable I stand by them, but in order for us to focus on Grid2 though I sugar coated & rephrased it. So far I have tediously walked about 20 people through grid setup. I do not tell them to hate the inverse color scheme. I explain it to them. Every single one has asked for it to be fixed to be like a regular unit frame. About a third refuse to even use Grid unless it can be made to have standard colored & behaving bars. These are not rank noobs. These are people that use sRaidFrames, X-Perl, etc.
If anyone gets angry because in my opinion the base default Grid is unusable u need to take a deep breath and calm down. It is just my opinion. The next thing to do is to take note of the implication that not everyone in the world wants Grid set up in the current default. It would be _nice_ to make it easy to switch. When your users tell you they have to constantly do the same thing over and over again ... u have an opportunity to do a better job.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
On initial load, all of the font/texture dropdown selections are blank; I am able to open the dropdown and select a font/texture, but the frame is never updated to reflect this. I formed a raid group for testing purposes; the first frame was displayed with the default Blizzard texture, while subsequent frames were displayed with the Grid gradient texture.
On a more general note, I have a few questions:
1. Will the "blink" behavior be optional? I do not ever want anything on Grid (or any other part of my UI) to blink, flash, shake, or otherwise animate. Astigmatism is annoying enough when viewing static images; while some people with normal vision may find blinking useful to grab their attention, it just makes the blinking object more difficult for me to see, and makes the things around the blinking object more difficult to focus on.
2. Will the "text2" indicator be optional? I prefer to have only a single center text indicator, in the middle of the frame.
Yes. I have quickly added options for the Blink module, and a "None" effect.
I suspect so.
I'll post errors just in case u wan't them.
on initial loading /grid2 i get:
and trying to change texture:
But as mentioned main features which i want/need it for works nicely ;)
Grid+Grid2
screen deleted
What is the cooldown monitor addon near the center of your screen?
@Jerry:
I've modified my local copy of Grid(1) to allow me to display dispellable debuffs using their cure spell icon rather than the debuff icon. For example, if someone has Wound Poison on them, and I have the Dispel Poison spell, I see the Dispel Poison spell icon instead of the Wound Poison debuff icon. I find that this makes it much faster to recognize what type of debuff it is. The icon border that Pasta added is a nice touch, but it's just not enough. Anyway, I would greatly like to see this feature in Grid2, both because I'd rather not have to keep copying and pasting code every time there's an update, and also because I think it would benefit other people greatly as well. I can send you a diff against Grid if you're interested.
Its oCD 2.4 with modify borders
I mean, the vertical one?Plus, my guildmates' life isn't showing the same way as yours? Special layout, maybe? Or did I miss something?
On my screen Grid2 in bottom right part, vertical layout - its my layout Grid (not Grid2).
Froum, look at PM
* Grouped Buffs. Right now GroupStatusMissingBuffs (badly named) does this. It groups related buffs together, mark + gift of the wild, welfare priest spell + prayer version, welfare blessing + greater blessing. This lets me assign a single indicator to both buffs (they are equivalent) and see who is missing it (show when missing option for buffs). It is ok for this to still need a plugin as so very few spells need it (as long as the show indicator when buff is missing option is standard). However without this ability you just can not use Grid for buffing.
* The side indicators. The 4 that come with grid are just not enough. I am not interrested in how a combination of overlays, blinking lights, cryptic color codes etc. can turn 4 little squares into all the indicator status u could ever need. They can not and do not. (Yes I have posted on this in the grid forum b4 ;-p) As an example, my druid needs to track total hots, both swiftmendable hots from any druid, all 3 hots I cast, including the lifebloom stack.
* Idealy there is just a given set of the "corner" indicators (at least 8, psossibly the 3 per corner ones) and you pick exactly which ones to activate from the setup ui. So if you want to you can have top, top left, top right, bottom left 1 2 & 3, bottom right.
* Same with icons. I would love to have 3 icons side by side, with my curable ones left and right and Raid Debuff in the center. This would eliminate dying due to lack of healing / curing just because some icon obscures another.
* I am keen on seeing the blinking thing used to indicate buff expiry. I am hoping it can blink more rapidly as the buff dies. It would be totaly nice in raid to have long duration buffs start blinking 10 minutes b4 expiry so they can be refreshed for a boss.
* For the settings UI I would kill for a one button switch from everything is dark and dismal to all bars are bright and shiny like regular unit frames. It is just as valid to set up grid that way as "everything is dark except stuff that needs attention". The very first thing I have to tediously walk people through is getting it to have a sane display of health that fits standard interface conventions as seen in bar graphs, stuff on the nightly news, all other unitframes.
* Ok this one is something that is an issue in AutoBar as well: if you have more than one character then the standard Ace profile system is total garbage. It is simply not the case that you set up common stuff, copy it around and never ever change it again. Instead you have a bunch of common settings that you may want to adjust from time to time as you get new plugins or tweak your interface etc. You also have a bunch of class specific settings. For instance, stuff I can cure status 1, 2 and 3 (pallies can cure 3 things I think). Or buffs I can do 1-whatever. Or maybe even character specific nuttiness like my raid leader enables seeing absolutely every buff, debuff, etc. in existence.
Anyway some things to chew over. Oh yeah and I added http://wowace.com/wiki/Grid/Guide/Healers, a first cut at a druid layout.
phanx's idea of using the cure spell icon instead is very nice.
as far as buffing. seems like Grid handles this pretty well to me. it can be set up to show when a buff is not on the target correct (not real sure, showing when the buff is on the target has always worked for me)? other than paladin blessings, which i would not use Grid for anyway, i think it can handle buffs just fine.
It's not about how easy something can be implemented, and it's also not about being able to turn them off. Grid's concept is minimalistic. If people want additional functionality, they'll need to install additional modules.
It's "opt-in", not "opt-out".
PS: we have to find a naming convention to prevent new users from installing Grid2 with *all* possible modules from the svn.
While not having been in touch with Jerry lately, keep in mind that Grid2 is in heavy development. Nothing you might see in a build or two is set in stone. You might see many things pop up and disappear again, I suppose Jerry is just making sure that optional modules will work correctly. The decision on the final default configuration has not been made, and it won't be made in the next days either.
I strongly disagree with your assessment in that wiki page that Grid is "useless as is" for healers. I've added my comments on the wiki discussion page; I concur with Maia that "regular" unit frames would meet your needs far better than Grid, and will probably rewrite that page to keep it more in line with the developers' concept of Grid, which I feel is more than sufficient for effective healing (with the exception of druid HoT management as noted in my comments).
As for the Grid2 stuff, I hope that the mana bars, no matter how "efficient" they are, are removed from the Grid2 core.
I also do not feel that any of the things listed in Toadkiller's post belong in the Grid2 core. Some may be necessary for certain classes, but class-specific features should stay out of the core. Buff grouping is really only useful for druids, mages, and priests. (Paladin buffs are simply too complex to manage this way and are better suited to a separate addon like PallyPower, although there was an interesting discussion in the PallyPower topic a while ago about a PallyPower Grid plugin.) Fine-grained HoT management is only useful for druids. Toadkiller may feel that 4 indicators are not enough, but I don't even use all 4, and can't think of anyone but druids who would need more than that. Multiple icons, multiple corner indicators, and buff duration tracking are far more clutter than Grid was ever designed for. Please keep Grid2 as basic as possible; if it's extensible via plugins, then there is zero issue with people writing plugins to add 500 icons and 1000 indicators and 12 mana bars, but none of this stuff should bloat up the core pacakage.
Edit: Many errors!
On opening the config:
On attempting to change the bar texture:
Statusbar and font selections do not work.
I have no idea why you would need to learn that; the center icon should work fine for missing buffs.
As this information has absolutely no bearing on actual gameplay, I don't think it belongs on unitframes at all. If you can't remember who is the master looter, it's fairly straightforward to open the raid panel and check. Grid frames should contain only the information you need to make gameplay decisions, such as who to heal, or who to dispel poison from, or who needs a Blessing of Protection.
I disagree. I believe that the focus should be on starting people with only the core addon (which would contain only the basics, and no class-specific stuff), and adding plugins only to fill specific needs. This is in contrast to the current system where the norm seems to be to install everything that has "Grid" in its name, and weed out the duplicates/nonfunctional/unnecessary plugins afterward. I also believe that no plugins should be officially endorsed as "mandatory" or "recommended"; there is no single set of plugins that will meet everyone's needs, which is why the plugin architecture exists in the first place. In fact, out of your list of nine plugins, I think five are totally unnecessary and have never used them or wanted their functionality. If you need them to play, then by all means, download and use them, but don't try to push your personal preferences on others. We already have enough issues with new people and plugin overload. Keep the core simple, and keep plugins small and focused.
It's simpler both from a development standpoint and a user standpoint to keep indicator modification/creation out of the core, and have new/modified indicators provided by plugins. From my point of view, none of those plugins are remotely necessary for Grid to be an awesome raid healing tool; why should I have to run the code to support them if I will never use them? Again, the plugin architecture was designed for exactly this reason -- if you want extra features such as those you mentioned, it's very easy to install plugins to provide them.
I think Jerry's pretty attached to the idea of in-game layout exporting/importing/sharing, but personally I'd rather not see any of this garbage in the core. Nobody else's Grid configuration can ever be as effective for you as one you create yourself.
Exactly, why write the core to force 4 on you if you only use 0, 1, 2 or 3? If you only use 3 why force an asymetric arrangement on the user? Why not let them pick topleft topright & bottom for example? Why not have the ability for the config to allow 1-16 square indicators to be activated? Unless activated the fact that you could have 16 is irrelevant to the user that only uses 2.
Similarly, why only 1 icon? Why not 2 or 3 or even 4? This still lets a user use 0 or just 1, but if they want to they can use more. "reducing to the max" is fine as far as it goes, but at some point you are losing the ability to be effective. Forcing both debuff icons into one icon indicator is just not optimal for me. Sometimes players have multiple debuffs. Sometimes they have boss debuffs on top of that. Shoving that into the same icon leads to wipes or forces me to disable some and so be less effective.
For my mage I want exactly 1 square indicator for buffing, 1 icon for curing stuff, 1 icon for boss debuffs. Thats it, dont care about anything else. Old grid was obese for this. Grid2 sounds like it can be slimmed down closer to what is needed. I hope layout information can be separated from the rest so my tiny mage Grid can still line up on one side with my much larger druid Grid in my overall UI.
Please lets not be silly. I like grid, I just want provision for more flexible basic features than it comes with. And I cannot stand the default inverse color scheme. As stated I am happy with specific stuff like the combined buffs being in plugins. The druid stuff definitely will be in plugins.
As for my comments about the default grid not being usable I stand by them, but in order for us to focus on Grid2 though I sugar coated & rephrased it. So far I have tediously walked about 20 people through grid setup. I do not tell them to hate the inverse color scheme. I explain it to them. Every single one has asked for it to be fixed to be like a regular unit frame. About a third refuse to even use Grid unless it can be made to have standard colored & behaving bars. These are not rank noobs. These are people that use sRaidFrames, X-Perl, etc.
If anyone gets angry because in my opinion the base default Grid is unusable u need to take a deep breath and calm down. It is just my opinion. The next thing to do is to take note of the implication that not everyone in the world wants Grid set up in the current default. It would be _nice_ to make it easy to switch. When your users tell you they have to constantly do the same thing over and over again ... u have an opportunity to do a better job.