If it's optional, then it shouldn't be installed by default, imho.
break19
Rule of thumb: required dependency is for modules
Optional dependency is used (by some) for libraries, but I don't think that is even correct. Personally, LoadAddon is a better choice than OptDep, because optdep forces it to load earlier than it needs to (for no good reason).
If it's optional, then it shouldn't be installed by default, imho.
break19
Alot of AddOns i know choose stuff to be optional so that people are able to disable/remove it without breaking/hacking the addon. Makes perfect sense to me, and alot of others too, apparently.
Like LibHealComm for example. Addons support it, and even package it by default, but its not required for the addon to function, so its support is designed to be optional. Perfect design in alot of aspects.
Don't think so... yet. I've heard of some stories where Pitbull modules stopped loading though, and it has to do with the ReqDep/OptDep/LoD/IsAddOnLoaded/ReloadUI mess.
See the UI forums thread.
Any libraries/addons relying on OptDep/ReqDep to be loaded, need to unset LoD for the duration of patch 3.0.2. It will be fixed in 3.0.3.
This does NOT affect addons/libraries that get loaded via explicit LoadAddOn() calls, such as addons loaded by e.g. AddonLoader.
LibRock and Ace2 libraries should be unaffected, as both LibRock and AceLibrary use LoadAddOn when needed.
Glad to head the upcoming fix and that AddonLoader isn't affected. :)
Indeed. I kept a list of libs i fixed and will revert the change once 3.0.3 hits and fixes the bug.
So, yeah, don't set your libs back to LoD just yet.
Edit: My own test case was ReqDepped. Good thing I tested that I guess.
Err, I tested. Seems fixed to me in 3.0.3!
Edit after further tests:
OptionalDeps on LoD addons is fixed.
But RequiredDeps on LoD addons is not fixed.
Followup posted here:
http://forums.worldofwarcraft.com/thread.html?topicId=10971929880&postId=123275959757&sid=1#10
Addons shouldn't generally ReqDep on a Lib, should they?
Can i restore the LoD to the libs where i removed it from?
Paste the list of Libs that you modified, so we can take a look and see if any of those libs are special enough to have addons ReqDep them?
Thats the list my script stripped the LoD from and would add it back
I hope it never does, its an ugly hack, and it really should not modify the .toc like this without any explicit control tags.
What if i have a library thats purely optional, but i package it by default? In disembed mode, its not optional anymore? :D
And it would break the LoD again =P
If it's optional, then it shouldn't be installed by default, imho.
break19
Rule of thumb: required dependency is for modules
Optional dependency is used (by some) for libraries, but I don't think that is even correct. Personally, LoadAddon is a better choice than OptDep, because optdep forces it to load earlier than it needs to (for no good reason).
Alot of AddOns i know choose stuff to be optional so that people are able to disable/remove it without breaking/hacking the addon. Makes perfect sense to me, and alot of others too, apparently.
Like LibHealComm for example. Addons support it, and even package it by default, but its not required for the addon to function, so its support is designed to be optional. Perfect design in alot of aspects.
http://forums.worldofwarcraft.com/thread.html?topicId=12354805813&sid=1