Not sure if there's a point in trying to give some constructive feedback based on how touchy people seem to be here.
So I'm just going to toss in my opinion and move on.
Rock is not user friendly
Stop dev on it until you can find someone that knows how to do usable UI dev.
I'm also pretty disappointed to find out that pitbull uses it now as its config. I loved that addon, but I'm running into a lot of config bugs suddenly and trying to find options in rocks is a horrible experience.
oh well time to find some new unit bars and maybe see if rock will ever trully mature into a usable config framework a long time from now
last comment - Just because a developer thinks an app is easy to use does not mean that it is actually easy for anyone else to use - remember the developer often forgets what things are new or even not visible, where as someone else can't see what's not visible and doesn't automagically know what they didn't know before
Not sure if there's a point in trying to give some constructive feedback based on how touchy people seem to be here.
So I'm just going to toss in my opinion and move on.
Rock is not user friendly
Stop dev on it until you can find someone that knows how to do usable UI dev.
I'm also pretty disappointed to find out that pitbull uses it now as its config. I loved that addon, but I'm running into a lot of config bugs suddenly and trying to find options in rocks is a horrible experience.
oh well time to find some new unit bars and maybe see if rock will ever trully mature into a usable config framework a long time from now
last comment - Just because a developer thinks an app is easy to use does not mean that it is actually easy for anyone else to use - remember the developer often forgets what things are new or even not visible, where as someone else can't see what's not visible and doesn't automagically know what they didn't know before
alt + right click on your player frame. open's rock config straight to the player frame, the options are in the same order as before. l2 config?
After toying with the new Rock config for Pitbull, Cartographer and FuBar I've found it leaps and bounds easier to use than the previous alternatives. Before you either had to rack your brain trying to remember each exactl slash command and variable to change or you had to rely on unpredictable and unreliable drop-down menus that would collapse or close for no reason.
Personally I like the new Rock and have tried to use it for every one of my Ace based mods and wish I could get the non-Ace ones to cooperate with it. I agree I had some issues with the Rock based mods when the library first came out, but it's nothing but smooth sailing now.
I absolutely hate the Rock config screen. It's ugly, and it's plain unecessarily big. When I just want to change a setting in raid, I don't want to bring up one big fat config screen. Drop down menu was good for that. I have extremely shit mouse, it floats all over the screen, and I have no problem with dew drop.
EG. I want to make the top bar not Auto hiddent. It used to be a matter of "right click / hover/ left click". Now it's a matter of "right click, hover all the way across the screen /scroll/ click (to open the fubar top bar tab) / click/ click".
Also, please can someone EXPLAIN. Why the hell on earth does a framework have the need to make the addons use it's config screen.
Lastly, if you think drop down menu "collapse or close for no reason", you need to L2Mouse. If an addon has tedious drop down menu, it's the addon author's slack. Not the problem of dropdown menu itself.
I don't care if it's rock/ace or wtever, bring back dropdown menu and give us option to disable that horrible looking config screen forever.
I absolutely hate the Rock config screen. It's ugly, and it's plain unecessarily big. When I just want to change a setting in raid, I don't want to bring up one big fat config screen. Drop down menu was good for that. I have extremely shit mouse, it floats all over the screen, and I have no problem with dew drop.
EG. I want to make the top bar not Auto hiddent. It used to be a matter of "right click / hover/ left click". Now it's a matter of "right click, hover all the way across the screen /scroll/ click (to open the fubar top bar tab) / click/ click".
Also, please can someone EXPLAIN. Why the hell on earth does a framework have the need to make the addons use it's config screen.
Lastly, if you think drop down menu "collapse or close for no reason", you need to L2Mouse. If an addon has tedious drop down menu, it's the addon author's slack. Not the problem of dropdown menu itself.
I don't care if it's rock/ace or wtever, bring back dropdown menu and give us option to disable that horrible looking config screen forever.
Also, please can someone EXPLAIN. Why the hell on earth does a framework have the need to make the addons use it's config screen.
sure.. ck's addon, ck's choice to use something else. Rock Config just happens to be something else he made too, and he chose to use it instead of dew drop.
it's more or less the same as an AceOptionsTable that dew drop uses.
There are so many concerns about this but really some of this I don't understand. Addons have always forced users to use "their style of config". In the older Ace2 world everybody was forced to use dropdown menus and possibly /commands.
It really comes down to personal preference. I loved it when Niagara/Waterfall came out because I preferred it over dropdown menues.
RockConfig is just Niagara. The only thing I miss from Niagara is Categories (which smartly enough was an option in Niagara, not a necessity). But RockConfig has embedded color selectors and nicer number sliders. There is good in both and with a suggestion that RockConfig support categories, who knows maybe RockConfig will some time do exactly all the stuff I liked about Niagara, plus some more.
I think adaptivity to different preferences is very good, but frameworks don't really necessarily stop you.
I don't know but in due time I can see someone write LibRockDewDrop (for a dropdown menu alternative) or LibRockTabConfig (for a tab based GUI) or LibRockCli (for people who like to macro their option changes).
Things are in transition so yeah it may not be exactly what you want right now... but isn't that how addons always have been? Take a non-ace addon: ItemRack. It does what I want closest to what I want. Hence I use it. Could I go complain how it doesn't do things exactly how I prefer it (i.e. open with the set I'm currently wearing?) Absolutely. But really there is no point.
Writing a polite suggestion and see if the addon-author agrees is a good way of going about. Or waiting/looking for an alternative you like. Or hack your own. In almost all cases having minor tolerance for some subjective difference to your personal ideal will make a lot of sense.
Also, please can someone EXPLAIN. Why the hell on earth does a framework have the need to make the addons use it's config screen.
It doesn't. Here's what happened:
One of the differences between Rock and Ace2 is the way the configuration options are fed in, as far as code is concerned. Therefore any addon switching to Rock became incompatible with the Ace2 configuration menus out there like Dewdrop and Waterfall. Obviously ckknight did not want users to be unable to configure their addons, so he wrote the RockConfig interface.
Whether RockConfig is handy or in the way is very situational. Most people used Dewdrop primarily when configuring their addons, but some of us preferred Niagara or other Waterfall-based configuration interfaces. Therefore, some people like RockConfig, and some people don't. However, at this point in time the most pressing problem (users having *no* configuration method) has been solved, and the current problem (some users being unsatisfied with the current configuration method) is far less urgent. ckknight does plan to write a dropdown menu lib for configuring Rock addons, however at the moment it is not his top priority.
Hopefully this has clears things up a bit. Please understand that RockConfig isn't an attempt to force GUI configuration on people - just to give them something to configure Rock addons with. Alternatives will be made available in time.
So I'm just going to toss in my opinion and move on.
Rock is not user friendly
Stop dev on it until you can find someone that knows how to do usable UI dev.
I'm also pretty disappointed to find out that pitbull uses it now as its config. I loved that addon, but I'm running into a lot of config bugs suddenly and trying to find options in rocks is a horrible experience.
oh well time to find some new unit bars and maybe see if rock will ever trully mature into a usable config framework a long time from now
last comment - Just because a developer thinks an app is easy to use does not mean that it is actually easy for anyone else to use - remember the developer often forgets what things are new or even not visible, where as someone else can't see what's not visible and doesn't automagically know what they didn't know before
alt + right click on your player frame. open's rock config straight to the player frame, the options are in the same order as before. l2 config?
Personally I like the new Rock and have tried to use it for every one of my Ace based mods and wish I could get the non-Ace ones to cooperate with it. I agree I had some issues with the Rock based mods when the library first came out, but it's nothing but smooth sailing now.
I absolutely hate the Rock config screen. It's ugly, and it's plain unecessarily big. When I just want to change a setting in raid, I don't want to bring up one big fat config screen. Drop down menu was good for that. I have extremely shit mouse, it floats all over the screen, and I have no problem with dew drop.
EG. I want to make the top bar not Auto hiddent. It used to be a matter of "right click / hover/ left click". Now it's a matter of "right click, hover all the way across the screen /scroll/ click (to open the fubar top bar tab) / click/ click".
Also, please can someone EXPLAIN. Why the hell on earth does a framework have the need to make the addons use it's config screen.
Lastly, if you think drop down menu "collapse or close for no reason", you need to L2Mouse. If an addon has tedious drop down menu, it's the addon author's slack. Not the problem of dropdown menu itself.
I don't care if it's rock/ace or wtever, bring back dropdown menu and give us option to disable that horrible looking config screen forever.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumQFT
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumsure.. ck's addon, ck's choice to use something else. Rock Config just happens to be something else he made too, and he chose to use it instead of dew drop.
it's more or less the same as an AceOptionsTable that dew drop uses.
It really comes down to personal preference. I loved it when Niagara/Waterfall came out because I preferred it over dropdown menues.
RockConfig is just Niagara. The only thing I miss from Niagara is Categories (which smartly enough was an option in Niagara, not a necessity). But RockConfig has embedded color selectors and nicer number sliders. There is good in both and with a suggestion that RockConfig support categories, who knows maybe RockConfig will some time do exactly all the stuff I liked about Niagara, plus some more.
I think adaptivity to different preferences is very good, but frameworks don't really necessarily stop you.
I don't know but in due time I can see someone write LibRockDewDrop (for a dropdown menu alternative) or LibRockTabConfig (for a tab based GUI) or LibRockCli (for people who like to macro their option changes).
Things are in transition so yeah it may not be exactly what you want right now... but isn't that how addons always have been? Take a non-ace addon: ItemRack. It does what I want closest to what I want. Hence I use it. Could I go complain how it doesn't do things exactly how I prefer it (i.e. open with the set I'm currently wearing?) Absolutely. But really there is no point.
Writing a polite suggestion and see if the addon-author agrees is a good way of going about. Or waiting/looking for an alternative you like. Or hack your own. In almost all cases having minor tolerance for some subjective difference to your personal ideal will make a lot of sense.
It doesn't. Here's what happened:
One of the differences between Rock and Ace2 is the way the configuration options are fed in, as far as code is concerned. Therefore any addon switching to Rock became incompatible with the Ace2 configuration menus out there like Dewdrop and Waterfall. Obviously ckknight did not want users to be unable to configure their addons, so he wrote the RockConfig interface.
Whether RockConfig is handy or in the way is very situational. Most people used Dewdrop primarily when configuring their addons, but some of us preferred Niagara or other Waterfall-based configuration interfaces. Therefore, some people like RockConfig, and some people don't. However, at this point in time the most pressing problem (users having *no* configuration method) has been solved, and the current problem (some users being unsatisfied with the current configuration method) is far less urgent. ckknight does plan to write a dropdown menu lib for configuring Rock addons, however at the moment it is not his top priority.
Hopefully this has clears things up a bit. Please understand that RockConfig isn't an attempt to force GUI configuration on people - just to give them something to configure Rock addons with. Alternatives will be made available in time.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator