• posted a message on Advanced Trade Skill Window

    Well, I'd also suggest you to not take this project over. But not because of any legal issues - I totally don't object against anyone taking anything, parts of code or the whole codebase, out of this project to continue the addon or create a new one or whatever. The "all rights reserved" license was probably a bit misleading, so I changed it to "public domain" now.

    So legal problems wouldn't be the reason, but technical ones. Most of the ATSW code is just ugly as hell, and it is full of funny chances for race conditions and performance bottlenecks. One of the reasons why I didn't continue development of this addon (besides the simple reason of me not having played WoW anymore for years now) was that it has grown to be unmaintainable over the first years of active development, probably mostly because of lack of an emphasis on writing maintainable and well-structured code on my side. I really wouldn't want to inherit such a wreck, so I can't suggest anyone else to do so. I'm not much into the Skillet codebase, but the last time I've glanced at it (quite some years ago, when it was just released) it seemed to be much better from a maintainability point of view, so it might be a good idea to invest your effort there.

    But if there's anything you find useful in the ATSW codebase, feel free to take whatever you'd like! I certainly won't do much with it anymore - I have basically just updated the TOC versions over the last years while the main functionality was at least mostly working without requiring any changes, so people could still use the addon. But of course it was just a matter of time for some API changes to seriously break important functionality - I guess this time has come now, so I'm going to finally abandon this old project once and for all.

    Link Removed
  • posted a message on MineSweeper

    Okay, I give up ;-) I've never analyzed Chronos in such a depth (actually I haven't analyzed it in any way, shame on me) and a resource waste is of course a very good argument against the usage of chronos (although, as I understood Rowne, he doesn't banish dependencies in general, but just the chronos function library). And since he already did the work to remove the chronos dependency from minesweeper, I would be stupid to not include his solution into the next version. So I ask you, Rowne: would you permit this? (Of course you'd get a note in the credits!)

    Link Removed
  • posted a message on MineSweeper

    37 addons and none of them uses chronos or sea? Woah...the first (well, maybe the second) addon I installed made me download chronos and sea, seems as if I had bad luck or something. And I'm not using any "big" addon, too...just a few (somewhere around ten) "normal" addons.

    Nevertheless you are right about the update thingie. On that one I more or less blindly trust in the chronos developers hoping that they know enough about software development that they change only their internal routines if they find that necessary and keep the interface the same. If they do so, there should never be any conflict between minesweeper and chronos. At the moment minesweeper does use chronos just to do some timing stuff, since the WoW developers seem to have missed to include some easy way to do that (although I also might have just not found it, this is my second addon and I'm definitely not a pro on that subject yet - in that case I would be happy to get a hint ;-)

    Oh yes, and I'm really sorry about the mistake, I actually did think you were complaining...my first thought was "oh man, that guy is just too lazy to download a few kilobytes of shared libraries", and I have to admit I was a little angry because downloading and installing those libraries take just a tiny fraction of the time I need to make minesweeper independent from chronos in a clean way. Now I know you also had your reasons for that suggestion and that they aren't based on any lazyness, but on conceptual thoughts.

    Link Removed
  • posted a message on MineSweeper

    ...but for a reason. Of course I could eliminate any dependencies (in the most simple way by just copy-and-pasting the code from the function library - chronos in this case - to my own addon), actually any addon developer could do so and make his addon "dependency free". But as I said: the concept of dependencies is there for a reason. If you have lets say 10 addons installed which all need some timekeeping functions (provided by chronos) and/or some other very common functions (provided by sea) and each developer had placed that code in his/her own addon, you would end up having the same pieces of code ten times on your harddisk. This does a) use up disk space (well, not so much that it would really matter considering todays disk sizes) and b) slow down the UI startup procedure, as the lua parser has to load x times the same code (something that definitely matters). It also makes compatibility issues MUCH more complicated and increases the chance for them to appear.

    I hope you can see why I'm going to stick with the dependency principle. So please just put Chronos and Sea into their appropriate places and have fun :-) you'll see that you will probably need those libraries again the next time you find an addon you like, but at that time you won't even have to think about it as you already have the libraries installed.

    Link Removed
  • To post a comment, please or register a new account.