so it's back to 20+ folders in the addon dir? sigh...
who cares? I don't look at the addons screen all days. At least things are sorted alphabetically, so screw it .. A one folder version would be nice, but we're not living in a perfect world.
Why do you guys use it? Seriously..im interested in the answer, because 1) it causes lots of problems for me when I try to distribute my addons, and 2) Standalones are better (technically)
I'm curious why are standalones better technically?
I've been using !!!Libs for some time now, main reason being reduced load times and reduced SVN checkout times over embeds (I update my addons regularly from SVN). I preferred that over standalones because I like my addons folder clean (I tend to fiddle with it maybe too much), and also WAU is a no-go, since I'm a Linux user (it's somehow ironic that WoW can run perfectly through Cedega while WAU cannot :P ).
Anyway, I'm not complaining, you're the authors and you do what you want to keep things simple and clean, I can just change my update script to reflect the new order. :)
oh have nothing to do with, that I can't handle all the extra addons, it's when I add them to a InstallShield installer that I have the problems since I group the addons to enable users to choose which adds to use:
embeded libs triple the amount of files I need to add to the groups.
Why do you guys use it? Seriously..im interested in the answer, because 1) it causes lots of problems for me when I try to distribute my addons, and 2) Standalones are better (technically)
I'm curious why are standalones better technically?
I've been using !!!Libs for some time now, main reason being reduced load times and reduced SVN checkout times over embeds (I update my addons regularly from SVN). I preferred that over standalones because I like my addons folder clean (I tend to fiddle with it maybe too much), and also WAU is a no-go, since I'm a Linux user (it's somehow ironic that WoW can run perfectly through Cedega while WAU cannot :P ).
Standalones and !!!Libs will take the same amount of time to checkout, as they do the same number of update calls due to !!!Libs's externals (okey technically !!!Libs will take longer because it has to update it's root folder and make an update call for every embeddable lib... whereas standalones like Babble will pull down many embeds at once with one call).
Only the libs that are needed are actually loaded with standalones, !!!Libs loads EVERYTHING.
Standalones are supported by their respective authors, !!!Libs is a hackey throwntogether solution that is designed for SVN-updating users, but the majority of it's users were getting it from out of date zips.
For the lib authors, standalones have all the advantages. The only complaint is "too many addon folders," which I think we've made it clear that we value performance gains over purely cosmetic issues like crowded addon folders.
One thing that might be done to make migrating from !!!libs to !!!StandaloneLibraries a little clearer is to not name it !!!StandaloneLibraries. The exclamation points gives the impression that it's an add-on folder trying to load before other add-ons. People will be prone to dropping the whole folder in and then wondering why WinAce did not update the folders inside. Users of the !!!Libs distribution, in particular, will be prone to thinking that it follows that structure, since it's similar to what they were using before.
Also, I think the instructions file inside could be made a little less ambiguous. I know they're fairly simple instructions but "Copy these folders into your WoW addon path" could be interpreted both as copying them individually and as a group within the !!!StandaloneLibraries directory.
Minor items, I know, but I thought I'd suggest it.
oh have nothing to do with, that I can't handle all the extra addons, it's when I add them to a InstallShield installer that I have the problems since I group the addons to enable users to choose which adds to use:
embeded libs triple the amount of files I need to add to the groups.
You wrote an installer, you should be able to manage the ace libraries with it and run standalone without any issues at all. I dont know why you would be using embedded libraries with an executable installer.
Standalones and !!!Libs will take the same amount of time to checkout, as they do the same number of update calls due to !!!Libs's externals (okey technically !!!Libs will take longer because it has to update it's root folder and make an update call for every embeddable lib... whereas standalones like Babble will pull down many embeds at once with one call).
Only the libs that are needed are actually loaded with standalones, !!!Libs loads EVERYTHING.
Standalones are supported by their respective authors, !!!Libs is a hackey throwntogether solution that is designed for SVN-updating users, but the majority of it's users were getting it from out of date zips.
For the lib authors, standalones have all the advantages. The only complaint is "too many addon folders," which I think we've made it clear that we value performance gains over purely cosmetic issues like crowded addon folders.
Thanks for clarifying this, I didn't realize the standalone libs are only loaded when they are needed. That's neat, I see why it's a better technical solution. I value performance over cosmetic issues too, after all I'm using Linux. :)
Now, I have one question. Since I can't use WAU, I can't see what structure it creates. I believe what it does is same thing as individual checkouts from SVN of each library it contains, i.e.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorAnd tekkub deleted the old files, heh.
Use the embeds if you're concerned about that, they're there for a reason.
Yes, because we got sick of listening to people bitch about addon folders and dependencies.
and I care about the addon screen, since I make addon packs, and normal people don't know what all these new adds they see now are.
Also using !!!StandaloneLibraries gives me errors, so I'm forced to going back to the embds.
I know, all that wasted hard drive space, it's like another two pr0n pictures I can't fit now. v_v
have nothing to do with mb's, it has to do with loading all the files and having to group the files when making addon packs.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttp://ui.worldofwar.net/ui.php?id=3310
or did you see the batch files i made?
I'm curious why are standalones better technically?
I've been using !!!Libs for some time now, main reason being reduced load times and reduced SVN checkout times over embeds (I update my addons regularly from SVN). I preferred that over standalones because I like my addons folder clean (I tend to fiddle with it maybe too much), and also WAU is a no-go, since I'm a Linux user (it's somehow ironic that WoW can run perfectly through Cedega while WAU cannot :P ).
Anyway, I'm not complaining, you're the authors and you do what you want to keep things simple and clean, I can just change my update script to reflect the new order. :)
oh have nothing to do with, that I can't handle all the extra addons, it's when I add them to a InstallShield installer that I have the problems since I group the addons to enable users to choose which adds to use:
embeded libs triple the amount of files I need to add to the groups.
And not reporting those errors solves nothing.
Standalones and !!!Libs will take the same amount of time to checkout, as they do the same number of update calls due to !!!Libs's externals (okey technically !!!Libs will take longer because it has to update it's root folder and make an update call for every embeddable lib... whereas standalones like Babble will pull down many embeds at once with one call).
Only the libs that are needed are actually loaded with standalones, !!!Libs loads EVERYTHING.
Standalones are supported by their respective authors, !!!Libs is a hackey throwntogether solution that is designed for SVN-updating users, but the majority of it's users were getting it from out of date zips.
For the lib authors, standalones have all the advantages. The only complaint is "too many addon folders," which I think we've made it clear that we value performance gains over purely cosmetic issues like crowded addon folders.
Also, I think the instructions file inside could be made a little less ambiguous. I know they're fairly simple instructions but "Copy these folders into your WoW addon path" could be interpreted both as copying them individually and as a group within the !!!StandaloneLibraries directory.
Minor items, I know, but I thought I'd suggest it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYou wrote an installer, you should be able to manage the ace libraries with it and run standalone without any issues at all. I dont know why you would be using embedded libraries with an executable installer.
btw: I don't know how old this screenshot is ... AceLoot is no longer existing, it's FruityLoots since quite a while :P (check my sig)
Thanks for clarifying this, I didn't realize the standalone libs are only loaded when they are needed. That's neat, I see why it's a better technical solution. I value performance over cosmetic issues too, after all I'm using Linux. :)
Now, I have one question. Since I can't use WAU, I can't see what structure it creates. I believe what it does is same thing as individual checkouts from SVN of each library it contains, i.e.
svn co --external-deps http://svn.wowace.com/wowace/trunk/Ace2/
svn co --external-deps http://svn.wowace.com/wowace/trunk/BabbleLib/
etc.
Is this correct?
Thanks for your time.
yeah, is quite old I am using FruityLoots :)
seems those errors as mostly to do with some of the addons being updated to 2.0 when DL with WAU as I'm getting the same errors with embedded libs.