I like what I see so far, but I have a few comments/requests:
1. It seems like there has to be a better way to get into the config menu than typing "/archud config". The fact that it is a Dewdrop menu really implies that the gesture to get there should be a mouse click, eh? Could be Ctrl+Right click on title plate, could be a minimap icon, FuBar icon... lotsa choices.
2. I would like to be able to reposition the target information better. It would be nice to have more than "attach to top" and "attach to bottom".
3. I haven't yet looked at the code for the arcs, but are they replaceable? Can the arc "width" be set? (I don't mean how far they are from the center, but the actual width of the arcs themselves.)
I have seen FuBar_MailFu, FuBar_tcgTradeskills, OneView and my own FuBar_PoisonFu (all from SVN) do this. It seems most likely when/if one of the addons has been updated. (Which is strange, but that is the way it feels.)
I'm wondering if these problem addons are all new FuBar 2.0 addons and maybe all the rest are running through the 1.2 compatibility layer?
I went ahead and fixed the error the right way, including adding "Color" as a localized string to the English and German versions and checked it into the branches folder for ckknight to pick up if he wants:
I'm not supporting 1.0 plugins because I don't feel like it. That's the reason. It is too much of a pain to support multiple paradigms.
Really, if I could, I wouldn't even support 1.2 plugins, but that'd destroy the current userbase and I don't want to do that.
Good job, sir. Backwards compatibility is the work of the devil. It stifles creativity and innovation.
If an author of a 1.0 plugin isn't playing anymore then someone should take it over. If there is no interest, then it should die on the vine. This is the wonderful world of open source people. If you don't like what someone is doing, take the code and change it.
If someone else wants to create or update a fubar-compat-1.0 library, then that is also something that they can do. Building backwards compat into the system is a terrible idea. Using extension libraries for back-compat is the way to go.
I love what you are doing (for free) with this work. Keep it up!
0
A couple of quick questions:
1. It seems to not show all buffs that are applied to "player" (e.g. Frost Armor). Is this intentional or by accident?
2. Is the spacing between party frames configurable somehow?
Thanks! Love it.
0
5. How about showing buffs on "player"? Give me that and I can eliminate my unit frame entirely.
Thanks!
0
1. It seems like there has to be a better way to get into the config menu than typing "/archud config". The fact that it is a Dewdrop menu really implies that the gesture to get there should be a mouse click, eh? Could be Ctrl+Right click on title plate, could be a minimap icon, FuBar icon... lotsa choices.
2. I would like to be able to reposition the target information better. It would be nice to have more than "attach to top" and "attach to bottom".
3. I haven't yet looked at the code for the arcs, but are they replaceable? Can the arc "width" be set? (I don't mean how far they are from the center, but the actual width of the arcs themselves.)
4. What is "Druid Mana"?
Keep it up! Looks good so far.
0
I'm wondering if these problem addons are all new FuBar 2.0 addons and maybe all the rest are running through the 1.2 compatibility layer?
Just an idea.
0
http://svn.wowace.com/root/branches/FuBar_ClockFu/PProvost
Enjoy!
0
Far from perfect, it at least makes the problem go away until an update comes along.
0
Good job, sir. Backwards compatibility is the work of the devil. It stifles creativity and innovation.
If an author of a 1.0 plugin isn't playing anymore then someone should take it over. If there is no interest, then it should die on the vine. This is the wonderful world of open source people. If you don't like what someone is doing, take the code and change it.
If someone else wants to create or update a fubar-compat-1.0 library, then that is also something that they can do. Building backwards compat into the system is a terrible idea. Using extension libraries for back-compat is the way to go.
I love what you are doing (for free) with this work. Keep it up!
0