I copied my addons to my ptr client and I have to say that I saw the need for loads of "minor tweaking". Even is there is only one line that has to be updated in 50 addons, 50 addons has to be updated. If you need to download 50 addons it will take time.
I did not have to update 50 addons, and I have more than 50 addons I've written :P
God, had to go count... 55 addons "active", half a dozen other people's addons I've forked, and I don't know how many old addons that still work fine and I haven't had to touch in years...
One of the bigger breaking changes is the arguments to most of Blizz's framexml functions. This probably bites people more than anything, but it's very easy to fix.
I'd like to believe that people round these parts stopped using the the globals back with 2.0 and won't be hit with this at all. The only thing it *should* effect are people that are hooking blizzy script handlers... and there's very few cases where that is your only option.
The this/self change will affect many addon that uses frame scripts or ui elements. Bigger addons are more likely affected by "this".
Else it's very specific if something the addon used got changed. If you did look for combat log damage/heal events, yeah you will need to rewrite.
Problem with some changes is that addons run without error, they just don't run correctly, i.e. they produce results but they are kinda wrong.
For example I had some ui dropdown menu code that didn't throw errors but behaved weirdly without proper "this"->"self"ing. Some ui element related functions additionally had their arguments reshuffled, which can cause some hilarity/anguish.
Some addons can accidentally work despite still being written for "this" old style. Mostly by just not needing "this/self" in the scripts/func they get called.
But again I don't think it's worrisome. Actively maintained addons likely have had that and other transitions done already.
The this/self change has not been "forced", at least in the latest beta build. Whether Blizzard will eventually move along with it, remains to be seen. The default UI has been rewritten for sure, some arguments have been shuffled around, since new ones may have been thrown in the mix, but that mostly affects hooks and should be trivial to "fix". Other than that, the changes are pretty straightforward except maybe the new secure templates and hmm interface options ? In all honesty, we've seen way more "apocalyptic" patches (see combat log revamping and whatnot).
Thanks for fixing my mistake! I really appreciate that. I would say that it was just a spelling mistake of some kind, because it didn't make any sense, but you probably know that better than me anyway. Thanks a lot again! :)
I have to criticize you too, though. You're lacking in the punctuation department my dear. And there must be a letter or even two missing in the word "official" in your sentence. That missing letters could make it very hard to understand you. And pleaaase start your sentences with capital letters. It's better for the eyes and makes you more respectable in your function as a grammarnazi.
My Question stays. Weren't there any other parties interested in buying/hosting wowace? I can't believe that for example WoWInterface.com wasn't interested. I mean they did host wowace for some time in the past, right? Imho wowinterface.com would have been a better partner. Their credibility is much better than curses.com.
-- Edit: forget it, I'll just answer your question again.
No, there were no other parties involved or interested with the conversion of WoWAce. Kaelten, the owner and administrator of WoWAce, is also a Curse employee. I believe (and he can correct me on this) that after the hosting bills for the old WoWAce started to pile up he sought assistance in hosting the increasingly popular site. This help came from his employer because they were already an addon distribution method and had the infrastructure to hold the old WoWAce together.
However, the bandwith used by WoWAce continued to grow. It grew beyond the means Curse could provide for free, so Kaelten decided it was in the best interest of the Community to officially merge WoWAce into the Curse Network.