Maybe $capss() for "sentence" is easier to remember.
Nope, but feature request noted for a future update.Thank you very much for putting it on there.
Hmm, looking through the configuration and usage documentation at https://bitbucket.org/zoomorph/foo_discogs, I didn't see anything that needed access to a user's account information, since it looks like it's just doing lookups against the general catalog, not against a user's collection. The closest thing I found talked about fetching images, but the Discogs documentation implies it can also be done with Discogs authentication:Discogs Authentication
From that URL:QuoteIf you do not plan on building an app which others can log into on their behalf,so it's definitely not for this plugin.
The Image resource represents a user-contributed image of a database object, such as Artists or Releases. Image requests require authentication and are subject to rate limiting.Am I missing something?
It’s unlikely that you’ll ever have to construct an image URL; images keys on other resources use fully-qualified URLs, including hostname and protocol. To retrieve images, authenticate via OAuth or Discogs Auth and fetch the object that contains the image of interest (e.g., the release, user profile, etc.). The image URL will be in the response using the HTTPS protocol, and requesting that URL should succeed.
If you do not plan on building an app which others can log into on their behalf,so it's definitely not for this plugin.
With foobar2000 starting up at 670-680 MB, beta 2fdc8be and the stable release both need at least 825-835 MB (but today it was 850-860 MB, just to make things more random!) before dropping to more or less 700 MB. Beta 6cc1cbd drops from 800-810 MB to 760 MB.Mind though, that you should differentiate between total memory usage (i.e. via task manager) and SMP memory usage (via `window.TotalMemoryUsage`).
What is also hard to tell is how multiple panels, working together in a real usage set up, would actually perform: analytically speaking the single panel is better off with a lower peak, but a higher residual means that the overall uncollected garbage level is generally higherWhatever the case it should not `leak` anymore. That is, SMP average memory usage should stay mostly the same.