@OrionShock: Yes I know curse uses a WebService. I sniffed it and it would be possible to emulate the curse-updater by reverse engineering it (in fact, someone already did it in Python and it could be easily ported to C# with some adjustment). But I don't feel confortable to do this (maybe illegal?) and "crawling" and parsing Websites is totally legal. So unless curse opens their interface, i'll stick with parsing.
@funkydude: I already implemented some kind of "priority" queue in my dev-version. The problem is, that I only have mappings for wowace for most addons, not yet for curse. I'm still thinking about allowing everyone to add their mappings to the global mappings file.
@funkydude: I already implemented some kind of "priority" queue in my dev-version. The problem is, that I only have mappings for wowace for most addons, not yet for curse. I'm still thinking about allowing everyone to add their mappings to the global mappings file.
Every wowace project page has a link to the curse download page, couldn't you parse the page one time if you only have a wowace mapping for an addon?
Well in fact, the curse "Tag" should be the same than the WoWAce / CurseForge Tag. So I could do a quick Copy/Past/Replace. Will to that for the next release I.
Speaking of the next Release, I'm very close to the next Alpha which has the following Features:
- NoLib Support
- Site Priority (Settings, Drag n Drop)
- Mark Addons which have multiple Mappings
- Use 7Zip for Extracting and check for wrong Packages (like xchar)
The last point is the most interresting (in my opinion). There are many Addons which are packed the wrong way. (like xchar, it has no folder "xchar" in the archive, so if you unpack it, you'll end up having 20 Files in your Addons Folder..., or Necrosis lately, which had a Folder too much). So I added a simple check if the archive has a Folder with the AddonName in it's Root Structure and if not, it displays a Window with the content of the archive and a button, to open the Archive with the 7z File Manager so you can extract it yourself.
I now need to do some error checking and hope to have the next version ready tomorrow.
After this Release, I think I have all core Features implemented and I can focus on Version Checking and Detecting which Addons needs updating and only update those. After I implemented that, the first Beta will be released.
Or does anyone of you think I am missing a core Feature?
New Features:
- NoLib Support
- Site Priority (Settings, Drag n Drop)
- Mark Addons which have multiple Mappings
- Use 7Zip for Extracting and check for wrong Packages (like xchar)
- Added over 100 Mappings
New Features:
- NoLib Support
- Site Priority (Settings, Drag n Drop)
- Mark Addons which have multiple Mappings
- Use 7Zip for Extracting and check for wrong Packages (like xchar)
- Added over 100 Mappings
What is the purpose of the ArchiveContentForm window that opens after updating an addon?
I have a feature request: Changelogs
Can you display the changelog for an addon before updating it? It's annoying when I see an update, check the changelog for the goodies and it's just a localization update. There's really no need to update the addon in that circumstance.
Changelog summary at the end. After addons are updated, give a summary window with the addons' changelogs. This was a much appreciated feature in JWU.
It's annoying when I see an update, check the changelog for the goodies and it's just a localization update. There's really no need to update the addon in that circumstance.
...and with the new WoWAce system, you shouldn't ever be updating an addon in that circumstance unless WADDU is allowing mappings to Alpha builds.
@Eggi: The possibility to ignore addons will be implemented in the next release
@SpUpUz: Thanks :)
@shank: That is if an Archive looks like it's wrongly packed. Like, it has two folders before the addon folder or no addon folder at all. Can you tell me which addon it is? (xchar is one, it is missing the "xchar" folder inside the archive so the ArchiveContentForm appears so you can check it and manually unpack it if you want. As for the Changelog, I'll have a look at it and put it into my task list.
@Torhal: By default Waddu now prefers updating from curse instead from curseforge/wowace (can be changed in the Settings).
Hm, I updated about 10 addons this morning and it happened so many times that I'm pretty sure it happened with every update. Some were wowace updates, some were Curse. The ArchiveContentForm window doesn't look like it's displaying anything important. In the main area on the left, there is nothing under "---Archive" and there is nothing in the grey area on the right. If I hit the "Open with 7zip" button at the bottom, it looks like it opens 7zip with no parameters, because it just displays the contents of the c: drive. This may be relevant: 7zip is not installed in the default c:/program files..." directory, but I did update that setting in the options.
Yes, the addon gets updated. After the version checks all that's in the log is:
11/1/2008 9:46:03 PM: Information - Thread #3: Updating Omen from wowace
11/1/2008 9:46:04 PM: Information - Thread #3: Downloaded to C:\Documents and Settings\Shank\Local Settings\Temp\tmp2BE.tmp
What is the purpose of the ArchiveContentForm window that opens after updating an addon?
I have a feature request: Changelogs
Can you display the changelog for an addon before updating it? It's annoying when I see an update, check the changelog for the goodies and it's just a localization update. There's really no need to update the addon in that circumstance.
Changelog summary at the end. After addons are updated, give a summary window with the addons' changelogs. This was a much appreciated feature in JWU.
@SpUpUz and shank:
The problem is that the Path to your Temp-Folder has spaces in it and I forgot to quote the Path when checking the content. So it can't find the archive and so Waddu suspects that the archive is wrong.
Fixed it right now and should be good in the next release.
Sorry for the annoying Window for every update.
@funkydude: I already implemented some kind of "priority" queue in my dev-version. The problem is, that I only have mappings for wowace for most addons, not yet for curse. I'm still thinking about allowing everyone to add their mappings to the global mappings file.
Every wowace project page has a link to the curse download page, couldn't you parse the page one time if you only have a wowace mapping for an addon?
Speaking of the next Release, I'm very close to the next Alpha which has the following Features:
- NoLib Support
- Site Priority (Settings, Drag n Drop)
- Mark Addons which have multiple Mappings
- Use 7Zip for Extracting and check for wrong Packages (like xchar)
The last point is the most interresting (in my opinion). There are many Addons which are packed the wrong way. (like xchar, it has no folder "xchar" in the archive, so if you unpack it, you'll end up having 20 Files in your Addons Folder..., or Necrosis lately, which had a Folder too much). So I added a simple check if the archive has a Folder with the AddonName in it's Root Structure and if not, it displays a Window with the content of the archive and a button, to open the Archive with the 7z File Manager so you can extract it yourself.
I now need to do some error checking and hope to have the next version ready tomorrow.
After this Release, I think I have all core Features implemented and I can focus on Version Checking and Detecting which Addons needs updating and only update those. After I implemented that, the first Beta will be released.
Or does anyone of you think I am missing a core Feature?
Wouldn't it be better to open it with the program which is registered for that filetype (which can be easyly done in .net)?
Also possible, but 7zip needs to be installed anyway (at least if you want the "integrity Check" and rar extracting).
Do you know CAKE3 which is a wrapper for different archive formats/libraries?
Nope, first time I hear it, but it looks interesting. I will definitely have a look at it but not for the next release later today.
-edit-
And please add AtlasLootFu to the Subaddons of AtlasLoot. It´s integrated.
Also ItemRack has a new "Thread" on wowinterface: ID 4148
Here are the Download Links:
Updater:
Mirror1 Mirror2
Mappings File:
Mirror1 Mirror2
New Features:
- NoLib Support
- Site Priority (Settings, Drag n Drop)
- Mark Addons which have multiple Mappings
- Use 7Zip for Extracting and check for wrong Packages (like xchar)
- Added over 100 Mappings
Hope to hear some Feedback!
it's fantastic!! pls do not stop development! :D
I have a feature request: Changelogs
Can you display the changelog for an addon before updating it? It's annoying when I see an update, check the changelog for the goodies and it's just a localization update. There's really no need to update the addon in that circumstance.
Changelog summary at the end. After addons are updated, give a summary window with the addons' changelogs. This was a much appreciated feature in JWU.
...and with the new WoWAce system, you shouldn't ever be updating an addon in that circumstance unless WADDU is allowing mappings to Alpha builds.
@SpUpUz: Thanks :)
@shank: That is if an Archive looks like it's wrongly packed. Like, it has two folders before the addon folder or no addon folder at all. Can you tell me which addon it is? (xchar is one, it is missing the "xchar" folder inside the archive so the ArchiveContentForm appears so you can check it and manually unpack it if you want. As for the Changelog, I'll have a look at it and put it into my task list.
@Torhal: By default Waddu now prefers updating from curse instead from curseforge/wowace (can be changed in the Settings).
11/1/2008 9:46:03 PM: Information - Thread #3: Updating Omen from wowace
11/1/2008 9:46:04 PM: Information - Thread #3: Downloaded to C:\Documents and Settings\Shank\Local Settings\Temp\tmp2BE.tmp
same problem here.
Can anyone of you run this command line command:
<Your Path to 7z>\7z.exe l <Path to some Archive>
And post me the result? Thanks
@SpUpUz and shank:
The problem is that the Path to your Temp-Folder has spaces in it and I forgot to quote the Path when checking the content. So it can't find the archive and so Waddu suspects that the archive is wrong.
Fixed it right now and should be good in the next release.
Sorry for the annoying Window for every update.