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.
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".
well, honestly, the wowace.com search is broken. I've searched for "Incubator" (note, I even know that the search is caps sensitive, most users don't know that), and got three results, but not the main topic thread. Onl after searching via the advanced logic, a 25sec MySQL query and then returning to the normal search I got more results.
So don't blame anyone for not having used the search. Because, it's broken most of the time.
PS: yes, I know it's a pain to handle a search index for 200.000 posts, and probably we should alter the search box to use google instead.
I assume it's the sum for all items, each: (rarity quotient * ilevel * slot weighting). If it's not using a slot weighting, then it might be off (because the ilvl of the e.g. chest item is more relevant than e.g. a trinket).
Hmm, I have the feeling that we're at a point where some people prefer the old way (a simple icon without anything else), and others prefer more than one indicator, various border colors, stack counts, duration counts, etc.
Personally I havn't been raiding for the last 2 weeks, so I can't comment on the changes, but I hope that the basic functionality is provided via a simple and understandable menu, and everything else is hidden in an additional "advanced" menu. The goal of Grid is and was to have a fast, reduced UI for raiding (and mostly healers), and any additional option in the config UI can be one too many.
Alternatively I could imagine moving the very basics of the (boss triggered) debuff functionality to the Grid core (but thats decision has to be made by pastamancer and jerry), and having an optional module that provides options such as stack count, duration, etc.
If the target is in range but is on the other side of a wall by example, you get an error message about it not being in sight. But if he is out of range you get the gray hand....
There should be a resolution to this, as Healbot addon does this correctly. Isn;t it a pitty not to fix this? As this is the only thing that makes healbot better in someway. All the rest is better with grid+clique. Stopcasting my macros before spell cast is not a solution. In combat I happen to cast faster on the new target and won;t be nice to have the almost done casting stopped. isn't it?
Guys, even if some of you enjoy discussing this topic, please do it elsewhere. It's completely unrelated to Grid, and the Grid thread has been derailed enough.
whitetooth made a change to Grid in r75354 which seems to have changed the API and broken stuff, pastamancer reverted the change in r75372 three hours later. So all should be well again.
Stay here, use curseforge, use WoWI-SVN, use Google Code, convert to git and github... there's tons of solutions, find the one you like.
Oh please don't tell anyone about github. Until very recently I was able to see whats happening in the Ralls/Ruby world with a single click (watching the latest repo changes), and now people like you come out of nowhere and put other stuff up there too. I can understand why you're doing it, but the repo overview gets useless if you see a wow addon next to a C# project, a js library and ruby code. I wish they'd implemented tagging. Oh, pleeeease.
(tekk, don't take it personal. You're just the only wow addon author over there atm.)
cerbul, too bad I'm never close to my wow application when posting here, but as for the debuffs, you already have the chance of assigning different priorities to each type, and also to not displa debuffs you can't cure yourself too.
As for GridStatusRaidDebuffs, it contains a list of all 'relevant' raid related debuffs, usually casted by bosses. So if you're mainly into PvE raiding, then you won't need more than this optional addon and maybe showing the debuff types for debuffs you can cure yourself as border/corner, while e.g. keeping the boss debuffs as center icon.
1) Options: don't expect and additional options to be added to the Grid core addon. The simple reason is that the config we're currently using (dewdrop/waterfall) was not made for as many options as Grid already has, and we've had lots of feedback from new users telling us that they are completely lost when trying to configure Grid. Jerry is currently working on Grid2, and if all goes well, we might have a better configuration UI, which should allow some 'advanced' options.
2) Defaults: while the defaults are probably not as good as they could be, there's a reason why e.g. the health bar display is inverted when compared to all other unit frames: the brighter a uit frame, the more attention it needs. Plus, you'll always see the class of the unit, even if it's only at 5% health. If the 'missing hp' area is black (like in all the other unit frames), you don't have these two advantages. I suppose you've manually inverted the default display, as your comment regarding the mouse over highlight should not be an issue with the default setup.
3) Debuffs: you have two options: either use the GridStatusRaidDebuffs to only display the 'relevant', raid related (boss) debuffs, or manually add debuffs you do not want to be displayed at all (by creating them and then simply not binding them to a single indicator). Personally, I use GridStatusRaidDebuffs as center icon display, and only display debuffs I can cure myself as border color. Plus, I did add some debuffs I don't care at all to not show them at all, partly related to short timed, frequent PvP debuffs.
4) Spell Cancelled: I've been using Grid/Clique for 18 months now and very rarely had the problem that I tried to cast a spell on a unit the moment it moved out of range. I therefor don't see the major problem there (but maybe I'm missing something), plus this might be a limitation of the wow API. I haven't thought about it, but maybe you could use Clique to use some intelligent macros instead of spells that would cancel a spell if it's still in casting mode after a click (the grey hand).
Personally I'd prefer to only see the player unit frame with the MC status instead of displaying all other units as MCd. While it's true that everyone else is 'hostile', the player still is the only person that's mind controlled. It should easily be possible to 'invert' the display to make sure that not the entire raid turns red when the player is MCd.
0
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.
0
...by installing PerfectRaid, as it's the default layout there.
0
0
So don't blame anyone for not having used the search. Because, it's broken most of the time.
PS: yes, I know it's a pain to handle a search index for 200.000 posts, and probably we should alter the search box to use google instead.
0
I'm seeing tons of GridFrame.lua:632 errors. And I hate seeing errors in Grid.
0
Oh I believe that's highly relevant, but it's not worth spending half the day discussing it ;)
0
I assume it's the sum for all items, each: (rarity quotient * ilevel * slot weighting). If it's not using a slot weighting, then it might be off (because the ilvl of the e.g. chest item is more relevant than e.g. a trinket).
0
Personally I havn't been raiding for the last 2 weeks, so I can't comment on the changes, but I hope that the basic functionality is provided via a simple and understandable menu, and everything else is hidden in an additional "advanced" menu. The goal of Grid is and was to have a fast, reduced UI for raiding (and mostly healers), and any additional option in the config UI can be one too many.
Alternatively I could imagine moving the very basics of the (boss triggered) debuff functionality to the Grid core (but thats decision has to be made by pastamancer and jerry), and having an optional module that provides options such as stack count, duration, etc.
0
Guys, even if some of you enjoy discussing this topic, please do it elsewhere. It's completely unrelated to Grid, and the Grid thread has been derailed enough.
Thanks.
0
0
This is definitely not where it should be. It's a status, it belongs into the Status menu and nowhere else.
0
Oh please don't tell anyone about github. Until very recently I was able to see whats happening in the Ralls/Ruby world with a single click (watching the latest repo changes), and now people like you come out of nowhere and put other stuff up there too. I can understand why you're doing it, but the repo overview gets useless if you see a wow addon next to a C# project, a js library and ruby code. I wish they'd implemented tagging. Oh, pleeeease.
(tekk, don't take it personal. You're just the only wow addon author over there atm.)
0
As for GridStatusRaidDebuffs, it contains a list of all 'relevant' raid related debuffs, usually casted by bosses. So if you're mainly into PvE raiding, then you won't need more than this optional addon and maybe showing the debuff types for debuffs you can cure yourself as border/corner, while e.g. keeping the boss debuffs as center icon.
0
1) Options: don't expect and additional options to be added to the Grid core addon. The simple reason is that the config we're currently using (dewdrop/waterfall) was not made for as many options as Grid already has, and we've had lots of feedback from new users telling us that they are completely lost when trying to configure Grid. Jerry is currently working on Grid2, and if all goes well, we might have a better configuration UI, which should allow some 'advanced' options.
2) Defaults: while the defaults are probably not as good as they could be, there's a reason why e.g. the health bar display is inverted when compared to all other unit frames: the brighter a uit frame, the more attention it needs. Plus, you'll always see the class of the unit, even if it's only at 5% health. If the 'missing hp' area is black (like in all the other unit frames), you don't have these two advantages. I suppose you've manually inverted the default display, as your comment regarding the mouse over highlight should not be an issue with the default setup.
3) Debuffs: you have two options: either use the GridStatusRaidDebuffs to only display the 'relevant', raid related (boss) debuffs, or manually add debuffs you do not want to be displayed at all (by creating them and then simply not binding them to a single indicator). Personally, I use GridStatusRaidDebuffs as center icon display, and only display debuffs I can cure myself as border color. Plus, I did add some debuffs I don't care at all to not show them at all, partly related to short timed, frequent PvP debuffs.
4) Spell Cancelled: I've been using Grid/Clique for 18 months now and very rarely had the problem that I tried to cast a spell on a unit the moment it moved out of range. I therefor don't see the major problem there (but maybe I'm missing something), plus this might be a limitation of the wow API. I haven't thought about it, but maybe you could use Clique to use some intelligent macros instead of spells that would cancel a spell if it's still in casting mode after a click (the grey hand).
0