Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
Sorry lol ..Nose of the salmon is a belgian/flemish expression that I translated >.< Don't know why. It's like creme de la creme is in French. It means it's a very very very very very good thing.
As for helping in the development process, I think it's important the core team remains as small as possible, otherwise I fear we risk going into different directions as I think there is no functionnal specifications document :)
That said if you, Pasta or Jerry need help on developping a specific module and you have time to give general directions for it there's no reason I wouldn't want to be a small part of that. Is there a googlecode or discussion site somewhere or are you mainly coordinating through IRC / PMs ?
I've used Grid since it's inception and I'm pretty fond of it as is. I really hope it doesn't become as bloated as the other addons are. I'm a healer (priest) and I've configured it to every possible debuff that should be of concern to me while raiding.
While the setup and documentation can use some improvement, I don't want default settings for healers where I won't be able to change anything, just to dumb it down.
For background, I am an average computer user, and I learned how to use Grid pretty quickly, and configured it pretty easily. (see my setup in sig)
I've used Grid since it's inception and I'm pretty fond of it as is. I really hope it doesn't become as bloated as the other addons are. I'm a healer (priest) and I've configured it to every possible debuff that should be of concern to me while raiding.
While the setup and documentation can use some improvement, I don't want default settings for healers where I won't be able to change anything, just to dumb it down.
For background, I am an average computer user, and I learned how to use Grid pretty quickly, and configured it pretty easily. (see my setup in sig)
Most interesting. If it's possible would you mind posting the SV of it's setup?
I would like to seed a more simplified configuration option.
Having to Grid -> Status -> Auras -> Thing1 -> Enable and then go to a completely different menu to set how Thing1 is displayed is one of the most annoying parts of configuring Grid IMO. I would like to see a submenu on Thing1 to set the display options.
I don't see the need to e.g. change each color for a gradient hot indicator, or the threat level in percent for the threat display. We only need good defaults.
Just wanted to come back and comment on this again after using the GridStatusReadyCheck plugin... while the default colors are perfectly logical, I personally have a very hard time distinguishing the yellow "no response yet" indicator from the green "ready" indicator, but as there is no in-game facility for changing these colors, I've had to resort to editing the Lua.
Just wanted to come back and comment on this again after using the GridStatusReadyCheck plugin... while the default colors are perfectly logical, I personally have a very hard time distinguishing the yellow "no response yet" indicator from the green "ready" indicator, but as there is no in-game facility for changing these colors, I've had to resort to editing the Lua.
Well, then the colors aren't optimal. We can have that discussion as long as we want, but I'll always be the 'Apple' guy, and I'll never want messy programs like MS Office. :)
Heh. I agree with whoever posted suggesting an "Advanced" configuration... come up with your optimal defaults, and leave a limited set of options available by default, but let advanced users get at the full set of options. While better defaults may make Grid more accessible for new users, no defaults will ever satisfy every user.
Just about the wiki you compiled, for the layout-related stuff I think it would be best to let GridDynamicLayout out of the equation, it is essentially an automatically-generated namelist-based layout that changes according to your raid context.
Simply said I don't see how you could merge it into a core Grid, it is just extreme automation of something you could do by hand (assuming some sort of in-game editing or import/export for layout ends up as a Grid 2.0 feature). In that regard GridDynamicZoneSwitch falls under the same category.
I think Grid core should stay centered on three things : layout, status and indicators, automation of simple tasks should stay accessible to plugins but chugging them into core would be too akin to feature-bloating.
On another note I'd like to do a feature request for Grid 2.0 : instead of handling horizontal and vertical padding for cells (unitframe), implement a cell-padding and a group-padding, if you prefer cell-padding horizontal/vertical + group-padding but I'd really like to be able to have a sort of separation between my groups (it really makes sense in the case of layouts using the units per column feature).
I've decided to make some draft configuration screens I'd like to share with you. Please keep in mind that I have *no* idea about what's possible with AceConfig-3.0 (e.g. show and hide UI elements based on the current setting of a dropdown menu), and neither did I spend much time considering the limitations of the technical (modular) implementation. It's simply what I'd love to see as config screens in future versions of Grid, and in case someone with time, knowledge and interest likes them, feel free to implement them (or base your more realistic layout on them) in cooperation with Jerry and Pasta (unless they have good reasons for objections):
Won't quote the lengthy image maia, but that's about what I was talking about with more intuitive as well. You have my vote :P
I just have no clue how anyone could implement such a setup without planning to kill me: sometimes you have suboptions (like AFK, PVP,...) and then choose the indicator from the list of available indicators via a dropdown (and then define settings related to that kind of indicator), sometimes you have the option of using more than one indicator (e.g. in the inc heals pic), and then the settings below.
Maybe the more realistic version is to initially choose one indicator from a dropdown, then the related options appear, and below a button with "add another indicator", and once you click that button you have another dropdown to choose an indicator. So in theory you could assign each status to all indicators if you'd really want to. Oh, that idea is similar to the 'smart playlists' UI from iTunes.
Well, it's logically still a mess, it's a draft, but it's only here to gather input (UI-wise and technically).
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSorry lol ..Nose of the salmon is a belgian/flemish expression that I translated >.< Don't know why. It's like creme de la creme is in French. It means it's a very very very very very good thing.
Crazy, yes. Belgian, yes. Phrase .. why yes as well!
Give the girl a price!
No seriously, it must have slipped out somehow, I usually don't translated expressions like that.
That said if you, Pasta or Jerry need help on developping a specific module and you have time to give general directions for it there's no reason I wouldn't want to be a small part of that. Is there a googlecode or discussion site somewhere or are you mainly coordinating through IRC / PMs ?
While the setup and documentation can use some improvement, I don't want default settings for healers where I won't be able to change anything, just to dumb it down.
For background, I am an average computer user, and I learned how to use Grid pretty quickly, and configured it pretty easily. (see my setup in sig)
Most interesting. If it's possible would you mind posting the SV of it's setup?
Having to Grid -> Status -> Auras -> Thing1 -> Enable and then go to a completely different menu to set how Thing1 is displayed is one of the most annoying parts of configuring Grid IMO. I would like to see a submenu on Thing1 to set the display options.
I actually have it uploaded for a guildmate of mine: http://files.filefront.com/Gridlua/;9447369;/fileinfo.html
Just wanted to come back and comment on this again after using the GridStatusReadyCheck plugin... while the default colors are perfectly logical, I personally have a very hard time distinguishing the yellow "no response yet" indicator from the green "ready" indicator, but as there is no in-game facility for changing these colors, I've had to resort to editing the Lua.
Well, then the colors aren't optimal. We can have that discussion as long as we want, but I'll always be the 'Apple' guy, and I'll never want messy programs like MS Office. :)
I hope it reflects the current discussions.
Edit:
renamed the page according to Jerry's remark (i thought of 3 because of Ace3 ;)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWe'll see how it goes. It depends on how generic the new status interface will be to see if a GridAlert module is still possible.
On another note, I think that if a new version number of Grid is needed, then Grid 2 is more appropriate than Grid 3.0.
Corrected the version numbers on the wiki and subject. I got confused with Ace2 -> Ace3 and concluded Grid -> Grid 3.
Simply said I don't see how you could merge it into a core Grid, it is just extreme automation of something you could do by hand (assuming some sort of in-game editing or import/export for layout ends up as a Grid 2.0 feature). In that regard GridDynamicZoneSwitch falls under the same category.
I think Grid core should stay centered on three things : layout, status and indicators, automation of simple tasks should stay accessible to plugins but chugging them into core would be too akin to feature-bloating.
On another note I'd like to do a feature request for Grid 2.0 : instead of handling horizontal and vertical padding for cells (unitframe), implement a cell-padding and a group-padding, if you prefer cell-padding horizontal/vertical + group-padding but I'd really like to be able to have a sort of separation between my groups (it really makes sense in the case of layouts using the units per column feature).
Link: http://img29.picoodle.com/img/img29/4/1/30/f_gridconfigsm_4f8f238.gif
I just have no clue how anyone could implement such a setup without planning to kill me: sometimes you have suboptions (like AFK, PVP,...) and then choose the indicator from the list of available indicators via a dropdown (and then define settings related to that kind of indicator), sometimes you have the option of using more than one indicator (e.g. in the inc heals pic), and then the settings below.
Maybe the more realistic version is to initially choose one indicator from a dropdown, then the related options appear, and below a button with "add another indicator", and once you click that button you have another dropdown to choose an indicator. So in theory you could assign each status to all indicators if you'd really want to. Oh, that idea is similar to the 'smart playlists' UI from iTunes.
Well, it's logically still a mess, it's a draft, but it's only here to gather input (UI-wise and technically).