Originally Posted by Shoogar
Hmmm, for a), a something like GNU Patch for Windows (or other similar software) should be portable, so if the patch.exe, the patch file, and a batch file were extracted into the addon directory, the user could just run the batch file and it would do the rest.
For b), doesn't the software to generate the patch look at both files and generate the patch? If you developed your own version starting with what you did before, and maintained it yourself adding features and fixing bugs without going back to their version at all, whenever an "official" release were made all you should have to do is run the patch/diff software against your .lua and their current one, and you should get a valid patch for that version, regardless of how different they were.
|
(a) That's a whole lot of hoops to jump through to support someone else's addon.
(b) It is my understanding that they are still running a code obfuscator on their addon and not publishing the lua source they themselves are working with.
They've just adjusted it so it doesn't run afoul of Blizzard's addon policy in a very blatant and obvious way.
For that reason their lua code changes disproportionately between revisions and someone trying to fix the new one would have to start over duplicating all the work they did on the last one tracing functions and such.
(I'm assuming that's one of the reasons they still run an obfuscator on their code to discourage fan updates)