I will look at it but people do need some sleep occasionally you know.
Not rushing you at all, just trying to provide the community that does use master a workaround until the original is working again. It's nice to know that I was not the only one that saw this add-on as a necessity
Xuerian, Question: Have you though about folding the Xloot modules into the main project? IE: only 1 XLoot project listed instead of the 4 components seperated. The new .pkgmeta can unload the modules on curse.com.
Granted you'd have to alter the .toc or other files to load the modules while you dev on it..
Dridzt: Thanks for the work on it. Don't be daunted by SVN, it's rather easy. You might want to communicate with Mikk a bit if your fixes aren't making it out there or things are feeling rushed. Don't be daunted by him either, "Accomplished author" or not ;)
OrionShock: I was going to put 1.0 up, then I loaded it up and realized I had driven it back into a mangled state before I stopped working on it. Phatloot is a Ace3 stripped-down XLoot core for anyone interested. A functional upgrade to that was in the wowace branches, but I assume that's lost to the nether now.
As far as merging them, yes, I've thought about it, but my thoughts generally lead towards -separating- them instead of packaging them together.
Could merge them in project only and separate with pkgmeta, I suppose that could work too - it would make more sense than having separate projects..
Really, I was planning on getting back into working on Xloot -as I mentioned previously- at least cleaning it up and separating it.... But I cracked it open in a editor, stared at it for a few minutes, then closed it agian, getting nowhere.
When I touched it last, I ended up writing and re-writing code trying to make it as simple as possible after being bested by delightfully simple code like Butsu (Damn you, haste, damn you and your beautiful unitframe framework).
Dridzt: Have you tried my version? I didn't just update the .toc and push yaknow, I ran a whole bunch of tests, including XLootMaster with announcing enabled, including random distribution, testing /rolling, testing with the confirmation level set to greens...
1.0 is in branches/1.0. It's functional. .pkgmeta doesn't include embeds. Not all options are in the gui, the layout ("display") system needs to be merged back into the core, not making multiple layouts anyway.
I made a couple commits in each of XLoot, XLootMonitor and XLootMaster
with the last few differences between the last releases and my local working copy.
I tried pretty much every option both in party and raid and couldn't cause it to error,
so it seems at a good point atm.
I'll go around removing links to temporary uploads to avoid confusion,
and try to go through proper channels for changes in the future.
(apologies for causing a bit of chaos there Mikk, Xuerian)
I have 2 small requests :)
1. Does anyone know how we can select which file will be the default for download on Curse?
Not an alpha ofc, I mean among the ones getting published there (beta and release)
At the moment it seems default download sticks with the last "release"
despite it being older than the most recent "beta".
Am I missing something or are we forced to tag "release" to update the default download?
2. Would be nice if the most current betas could be updated to WoWInterface as well.
I can't do it as there's no joint-authorship facilities I could find.