Ya know what drives me bonkers? WHen CC installs an update to itself and doesn't provide any release notes. I know they're mostly bug fixes and such and most development is directed at 4.0, but I'd still like to see them.
Though there seems to be some confusion about whether it's the Curse site or Curse client under discussion, you might want to be aware of this ("Curse Gaming Seems to have been hacked") thread on the WoW forums.
Had the same with libDualspecc used by RangeDisplay.
Some folks are having the same problem with my addon (Auracle). The with-libs packages built by WoWAce seem to be just fine, but when the Curse Client installs it disembedded-style, it skips LibDualSpec and now also LibOOP (my own lib).
No the client has not been affected by this outbreak. There were a few addon pages that got infected due to an obscure bug in the sanitization process for comments. These have been removed and the hole has been fixed in an emergency patch today.
The client's ads are very tightly controlled (exactly for this reason) and were not compromised.
Just wanted to say - I upgraded to Premium today and the Client handled the switch seamlessly. I'm really happy that I upgraded. I liked the Client before but it's even better now. I'm also happy to be contributing to the Author program. Cheers, Curse staff!
Finally tried v4 and I have to say it's a step back in UI design. It feels like it's using way less of the native window manager, and is slower, clunkier and less user-friendly as a result. Looks pretty though.
I do like that it ditches the concept of popping up status boxes in the lower-right corner (I think; maybe my memory is faulty on that?), and that it has a Submit Bug button (which I used to complain about the Submit Bug button :p)
Is there a possibility to have access to a beta (or alpha) of the curse client 4. I tried to install a few addon through the curse client 3 and lots of library were deleted after that :( (using disembeded and alpha)
That'd be awful nice, wouldn't it gagou? I just confirmed without a doubt that the current Curse Client is not always downloading extra libs in spite of the .pkgmeta listing them as externals. The most obvious because it skipped a ton of them was PitBull 3 -- after installing it, the only libs I had that it lists as externals were CallbackHandler, Babble-Zone, SharedMedia-3.0, and LibStub, because other addons had already pulled them down. I was missing Banzai, DogTag & DogTag-Unit, HealComm, all the Rock libs, and TalentQuery, and had to go download them all separately. I, too, run disembedded and pull alphas. I don't know if it's a different situation if I only use release or beta tagged addons, or if the Curse client's disembedded functionality is just flaky all around. I don't have quite that much time to play around with wiping my addons and changing install type extra times.
(Yes, I'm getting ready to go haunt the Curse bugtracker with the info, just ranting here.)
Pardon me, but why exactly do you guys disembed? The extra 2 seconds of time spent at the loading screen is too much for you? I was a die-hard disembedder, but then I just learnt to deal and my life has been so much simpler. The Curse Client will always be designed with disembedding as an afterthought, so why bother doing it?
Once the game is up and running, there's no difference in performance, no extra FPS to be gained. As far as I understand it the only difference is that the libraries take a little bit more time getting sorted out at load time. Whoopie.
Pardon me, but why exactly do you guys disembed? The extra 2 seconds of time spent at the loading screen is too much for you? I was a die-hard disembedder, but then I just learnt to deal and my life has been so much simpler. The Curse Client will always be designed with disembedding as an afterthought, so why bother doing it?
Once the game is up and running, there's no difference in performance, no extra FPS to be gained. As far as I understand it the only difference is that the libraries take a little bit more time getting sorted out at load time. Whoopie.
My main reason is perfomance monitoring. with disembeded i get a much clearer image of what eats my performance.
On top of that, it just seems silly to have 40+ copies of some of the same libraries. Call me crazy but I use what many would deem a ridiculous amount of addons, and many share the same libraries. It seems to me to be more efficient not to have that many duplicates all at once, even if the game is smart enough to only load one copy of them.
Regardless, if there is a mechanism for running this way, which doesn't seem all that complicated, why then would it seem to be half broken lately? I'm fairly certain it actually worked properly a few revisions ago; now it seems horribly inconsistent. Uninstall an addon, and it often uninstalls its libraries even if another addon also uses them. Install a new addon, maybe it installs its .pkgmeta-desginated libraries, maybe it doesn't. The bit of logic that reads an addons .pkgmeta and compares it to the other addons' data for what you've already installed just doesn't seem so complex that it should manage to be this inconsistent.
It seems to me to be more efficient not to have that many duplicates all at once, even if the game is smart enough to only load one copy of them.
The game isn't as smart as you think. The game always loads all 40 copies of the library. It's the code in the libraries that we write that checks to see if it should overwrite the version already loaded (basically a version check), or discard itself to the garbage.
The game isn't as smart as you think. The game always loads all 40 copies of the library. It's the code in the libraries that we write that checks to see if it should overwrite the version already loaded (basically a version check), or discard itself to the garbage.
A-ha, I didn't realize that. I'm glad addon writers are more with it than the game's addon checking is, then. Seems to me that onliy adds a point in favor of running with only one set of libraries across the board. The downside is a case where an addon needs, or at least expects, an older version of a library that it normally chooses to package instead of the newer version, and breaks because of a change in the newer version of said library. However, if two versions of the same library cannot run at the same time then that problem doesn't go away just by installing in embedded mode.
Embedding libraries was originally designed to make distribution of single addons easier. It is not arguable that there isn't _some_ sort of performance gain from running disembedded. What is true however, is that sometimes you don't always get authors who's addons will run right in both scenarios, and many people argue that the gains are minor.
Bottom line, I think it's a highly subjective topic and not one for which there is a clear right or wrong answer.
Regardless, if there is a mechanism for running this way, which doesn't seem all that complicated, why then would it seem to be half broken lately? I'm fairly certain it actually worked properly a few revisions ago; now it seems horribly inconsistent. Uninstall an addon, and it often uninstalls its libraries even if another addon also uses them. Install a new addon, maybe it installs its .pkgmeta-desginated libraries, maybe it doesn't.
This is the main reason I've been telling my friends -- even the programmers -- to not run disembedded. I run that way, and over the last week I've been bitten dozens of times by .pkgmeta libraries simply being ignored by CC. I know enough to find the name and install the library, but the fact that CC is silently dropping dependencies is reason enough to not run disembedded if you aren't already doing so.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumMy 2 cents.
Some folks are having the same problem with my addon (Auracle). The with-libs packages built by WoWAce seem to be just fine, but when the Curse Client installs it disembedded-style, it skips LibDualSpec and now also LibOOP (my own lib).
The client's ads are very tightly controlled (exactly for this reason) and were not compromised.
I don't really care if the release notes are in the client or available on the web.
I do like that it ditches the concept of popping up status boxes in the lower-right corner (I think; maybe my memory is faulty on that?), and that it has a Submit Bug button (which I used to complain about the Submit Bug button :p)
(Yes, I'm getting ready to go haunt the Curse bugtracker with the info, just ranting here.)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOnce the game is up and running, there's no difference in performance, no extra FPS to be gained. As far as I understand it the only difference is that the libraries take a little bit more time getting sorted out at load time. Whoopie.
My main reason is perfomance monitoring. with disembeded i get a much clearer image of what eats my performance.
And the loadtime is an added bonus.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumRegardless, if there is a mechanism for running this way, which doesn't seem all that complicated, why then would it seem to be half broken lately? I'm fairly certain it actually worked properly a few revisions ago; now it seems horribly inconsistent. Uninstall an addon, and it often uninstalls its libraries even if another addon also uses them. Install a new addon, maybe it installs its .pkgmeta-desginated libraries, maybe it doesn't. The bit of logic that reads an addons .pkgmeta and compares it to the other addons' data for what you've already installed just doesn't seem so complex that it should manage to be this inconsistent.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe game isn't as smart as you think. The game always loads all 40 copies of the library. It's the code in the libraries that we write that checks to see if it should overwrite the version already loaded (basically a version check), or discard itself to the garbage.
A-ha, I didn't realize that. I'm glad addon writers are more with it than the game's addon checking is, then. Seems to me that onliy adds a point in favor of running with only one set of libraries across the board. The downside is a case where an addon needs, or at least expects, an older version of a library that it normally chooses to package instead of the newer version, and breaks because of a change in the newer version of said library. However, if two versions of the same library cannot run at the same time then that problem doesn't go away just by installing in embedded mode.
Bottom line, I think it's a highly subjective topic and not one for which there is a clear right or wrong answer.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis is the main reason I've been telling my friends -- even the programmers -- to not run disembedded. I run that way, and over the last week I've been bitten dozens of times by .pkgmeta libraries simply being ignored by CC. I know enough to find the name and install the library, but the fact that CC is silently dropping dependencies is reason enough to not run disembedded if you aren't already doing so.