For me the part of grid that is really lacking is config. It is hard to convince people to use grid when after they load it up it requires laborious 30 minutes of customization just to get it into a happy state. & thats with someone helping them over teamspeak.
So really I mean the defaults are not useful. It sure would be nice if there was a way for a module to add class specific config ... hints? ... or something. Anything just to make it less painless.
As an alternative I have been dreaming of making a module that would specifically configure a few specific grid modules in a sensible way. It would have 1 or more config sets per class & you just click a button to set up everything all at once. But it would have no real way of accomodating new modules. Hence the need for new modules have some kind of system or something for their class specific stuff.
An issue is that the base grid is so flexible that there are probably 5 million configs out there. Such a mod would collate popular ones I guess or apply selective pressure towards common standards. At the very least it would get all the good config ideas out & available.
Example:
Let's assume GridStatusMissingBuffs remains separate (I think 1 or both of its features ought to be integrated). Well the thing it does is combine raid & welfare buffs & allow an inverted buff indicator. So for druids it is nonsensical to load up GridStatusMissingBuffs & then have to go make a Mark / Gift of the Wild indicator in a nice lurid pink. It should come with those standard as well as thorns (brown) & omen of clarity (teal) & they should have those custom colors assigned already. Omen should have a druid filter on it.
Same kind of deal for the other major buffers. Pallies would have to have a more complicated class specific setup.
Now if there was a scheme, kinda like localization but "classization" that each module implemented, then a config mod could just use that as is. Perhaps the process of doing this results in say 2-3 best practices configs. Maybe a labeling scheme to keep indicators from clobering each other for specific sets. So the "Amphibian Hater" set would have a base set using GridSideIndicators, GridStatusHotStack, GridStatusHots and GridStatusMissingBuffs. New modules that specified defaults for the "Amphibian Hater" set would have to not clobber the core set.
Oh yeah & automagically this stuff needs to do its thing if config menu is opened or on first startup for that "works straight out of the box" experience but then go away & use no extra memory / processing power...
For me the part of grid that is really lacking is config. It is hard to convince people to use grid when after they load it up it requires laborious 30 minutes of customization just to get it into a happy state. & thats with someone helping them over teamspeak.
So really I mean the defaults are not useful. It sure would be nice if there was a way for a module to add class specific config ... hints? ... or something. Anything just to make it less painless.
I could see allowing each module to specify per-class defaults. The hardest part would be getting non-core modules to update the status-map in GridFrame.
- possiblity to pass optional SetTexCoord(s) values via SendStatusGained
By default all icons are displayed with SetTexCoord(0.05, 0.95, 0.05, 0.95). This is ok for buffs/debuffs to get rid of the border, but if I want to show other (ingame)icons with texcoords (eg: RaidTargetIcons/PvP icons) this is a problem.
- order field in advanced options menu GridFrame.options.args.advanced.args (GridFrame.lua)
Mmm that reminds me. Right now I have mana warning at 40%, but really I would want to stack multiple warnings with various colors at different % so I can get a clearer view. So some kind of way to duplicate indicators with different settings?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumLet me know what you liked/didn't-like about the API, things you wish there was an API for, or any thoughts/musings you have about Grid modules.
For me the part of grid that is really lacking is config. It is hard to convince people to use grid when after they load it up it requires laborious 30 minutes of customization just to get it into a happy state. & thats with someone helping them over teamspeak.
So really I mean the defaults are not useful. It sure would be nice if there was a way for a module to add class specific config ... hints? ... or something. Anything just to make it less painless.
As an alternative I have been dreaming of making a module that would specifically configure a few specific grid modules in a sensible way. It would have 1 or more config sets per class & you just click a button to set up everything all at once. But it would have no real way of accomodating new modules. Hence the need for new modules have some kind of system or something for their class specific stuff.
An issue is that the base grid is so flexible that there are probably 5 million configs out there. Such a mod would collate popular ones I guess or apply selective pressure towards common standards. At the very least it would get all the good config ideas out & available.
Example:
Let's assume GridStatusMissingBuffs remains separate (I think 1 or both of its features ought to be integrated). Well the thing it does is combine raid & welfare buffs & allow an inverted buff indicator. So for druids it is nonsensical to load up GridStatusMissingBuffs & then have to go make a Mark / Gift of the Wild indicator in a nice lurid pink. It should come with those standard as well as thorns (brown) & omen of clarity (teal) & they should have those custom colors assigned already. Omen should have a druid filter on it.
Same kind of deal for the other major buffers. Pallies would have to have a more complicated class specific setup.
Now if there was a scheme, kinda like localization but "classization" that each module implemented, then a config mod could just use that as is. Perhaps the process of doing this results in say 2-3 best practices configs. Maybe a labeling scheme to keep indicators from clobering each other for specific sets. So the "Amphibian Hater" set would have a base set using GridSideIndicators, GridStatusHotStack, GridStatusHots and GridStatusMissingBuffs. New modules that specified defaults for the "Amphibian Hater" set would have to not clobber the core set.
Oh yeah & automagically this stuff needs to do its thing if config menu is opened or on first startup for that "works straight out of the box" experience but then go away & use no extra memory / processing power...
Anyway, you did ask for musings...;-p
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI could see allowing each module to specify per-class defaults. The hardest part would be getting non-core modules to update the status-map in GridFrame.
- possiblity to pass optional SetTexCoord(s) values via SendStatusGained
By default all icons are displayed with SetTexCoord(0.05, 0.95, 0.05, 0.95). This is ok for buffs/debuffs to get rid of the border, but if I want to show other (ingame)icons with texcoords (eg: RaidTargetIcons/PvP icons) this is a problem.
- order field in advanced options menu GridFrame.options.args.advanced.args (GridFrame.lua)