WUU suddenly stopped working for me today. I'm not sure what happened, but the process automatically ends itself almost immediately after starting. The WUU window never appears. The last time I was able to run the program to update my addons, everything seemed to be working fine until I tried to rescan my addons to refresh the list after updating(Since sometimes WUU likes to add what look like dependancies to my list even though that setting should be disabled.).
I had all of my download locations set manually for the better part of 155 addons. I'd hate to have to set that up all over again. Any ideas?
Yea, delete the addon "SellFish" for some reason, this addon is being improperly unzipped, and all files are being created with 0 length, and when WUU cannot read the TOC file, it crashes.
Or, you could just do what I, and my wife do.. I simply copy the Wow folder over to the other system, takes about 45mins on my wifi (54Mbps) network..
Had to do that a couple nights ago, when her laptop's HD died and we bought her a new HD.. instead of installing wow and doing all the updates etc, I just copied my installation over to hers. done and done.
Huh. It seems the culprit was Norton Internet Security after all. Disabling the components wasn't enough. I completely uninstalled it and I can update just fine now. Has anyone managed to successfully configure Norton to allow WUU to function properly? If so, how did you set it up?
Well, the obvious answer is, don't use Norton. Ever since Symantec took over the Norton stuff, it's all been on a downhill slide..
Back in the early 90s, Norton was the best stuff around. Now it sucks. More than sucks. In fact, most "Security suites" are a waste of time. I always recommend Panda stuff to my family and friends who still are stuck in the stone age, ie windows..
Since WoW was originally developed for Windows, which is case-insensitive (sometimes aggressively so), addon names *have* to be unique regardlss of case, so just doing a case-insensitive search should work as intended.
Wow was not originally developed just for windows. Blizzard has -always- had mac support in every single one of their titles.
Writing an application that is cross-compatible is fairly simple actually. It only becomes harder when game developers begin using more and more OS-dependant libraries to write their code. DirectX anyone? OpenGL was the original direct interface, so instead of MS improving the standard, they decided to write their own, and pushed for game developers to use it.
There are other things that need to be written a certain way, as well. But in many many cases, software can easily be compiled for multiple operating systems. Just look at how many different types of Unix there are: Linux, BSD, SystemV, BeOS(mostly), Mac OS X, the list goes on. Yet, almost all the apps that will run on ONE of these Unices will run on any of them. They just need to be compiled for that system.
Two ways of this are: distribute the source code, allow the end user to compile it for his system,
Compile multiple binaries for the OS's you intend to support.
They each have their advantages, and most (if not all) commercial applications choose the latter for the simple reason of keeping the code secret from their competition.
Thanks for the reply and tip about FishingBuddy. I've used the compilation version because I though downloading/checking one addon instead of 3 would be faster...
The problem is not about FishingBuddy per se, but more general one - as far as I understand it the Dummy addon FB_OutfitDisplayFrame shouldn't be extracted at all, but it is and contains ODF directory.
This time I have some larger feature ideas: I hope letters will be better then numbers ;) A) Unused addons cleanup
This one would need AddOns.txt parser and should report which characters use each addon and if some addon is not used it should recommend deleting it. This can be presented as sortable column displaying number of characters who has the addon enabled.
B) Unused libraries cleanup
What it should do is to check all library-type addons and when no addons are using them it should recommend deleting the library. The problem is, how to detect if it is library or normal addon - could be manually configured by the user. This can be also presented as column in addon list displaying number of addons depending on the addon.
C) Outdated addon report/Interface version report
Add another sortable column with addon interface version. This could be used to find outdated addons which needs replacing or updating by author.
"## X-Category: Library" tells you if it's a Library or not. :)
I used the Development Tools (Xcode) to build it.. I simply created a new project, made it a cocoa-python project, copied your python scripts into the project, and renamed WUU.py to main.py so the app would call the correct python script upon execution.
Also, you certainly -can- see that I used your source, as before, the scripts are available inside the app. Run a diff on WUU.app/Contents/Resources/*.py against your code (using the same version obviously. :)
Also you can change the scripts inside the app, (and rename WUU.py to main.py, obviously) and it'll run whatever you've put in there. :)
Interesting. I downloaded this to check it out, and my problem with the app crashing when I tried to download new addons from WowAce no longer appears. Different versions of Python in the two builds, I guess. Thanks, Break19!
Actually.. this one doesnt include python at all, but instead simply includes a stub to use whatever version of python currently resides on your installation. :)
Hey Lejordet, I have "recompiled" the mac OS X of WUU.. this time I used XTools, and reduced the size of the executable considerably.
It's now 1.1M, but will not work "out-of-the-box" for 10.4 or below. (this is because Leopard now ships with python 2.5, and previous OS's only had 2.3) However, installing the 2.4 version of Python will solve this issue.
For those of you curious, the version that Lejordet has on his main website -will- work with 10.4, but that is because the executable already includes the entire python 2.4 framework bundled inside..
The one I've just built leaves it out.
Another thing. This app bundle I'm using now, is also considerably faster than the old one, likely because of the Xtools "builds" the python source, and because it no longer needs to first load the entire python framework.
So.. for those of you on Mac OS X Leopard (10.5) I have attached the .app, it is built off of version 1.6.511(beta). If you have OS X 10.4, and have already installed python 2.4 or 2.5, please give it a go and tell me if it works for you.
note that the filesize of the zip is less than 300kB
The 504 update fixed the last problem, but... when it starts up, it says there's no addons, and a directory scan doesn't find any. I checked the prefs, and it's calling the wow directory (which is labelled as "where wow.exe resides", but never mind that) /Applications/World of Warcraft/World of Warcraft.app which is of course incorrect - it's /Applications/World of Warcraft/. The backup directory is similarly listed as /Applications/World of Warcraft/World of Warcraft.app/Interface/WUUBackup.
It appears that this updater has actually modified World of Warcraft.app, which may mean I'm gonna have to spend another five hours reinstalling the damn thing - by which I mean WoW - in which case, sir, you better hope we never meet in person. :-(
Problem is, the updater looks for the executable's directory, but doesnt consider the fact, that under OS X, the directory IS the executable..
Not sure why, but WUU is not opening a changelog file for me after it finishes updating addons, even if there are updates. Clicking the Changelog report item in the menu also doesn't bring up a changelog. Running the latest version of WUU on MacOSX 10.5.1, Firefox 188.8.131.52
Reading Comprehension FTL.. 2, maybe 3 posts up is a statement by the author saying he accidentally broke the updater, and will be releasing a fix with the next update..
Well.. I didnt even notice the missing dot until you pointed it out.. and I'd bet good money that is part of the reason my little change didnt make it work.. I will test, and get back to you on it.
EDIT: Hmmmm I changed the "friendly name" to Combuctor Beta 1, and it still says it cannot find the addon.. But that doesn't rule it out as a possible cause.. I think maybe by me doing that, it now cant find a decent version since all it sees is a 0 as a version and possibly kicks that out.. but this is all speculation until I break down and scan the code..