nperrier/sockso — comment on commit 94e43113f38dad3bc99e9e5515d8d3bdd645b858
File:  line 0
By nperrier:

I'm sorry, I'm horrible at design. I've refactored this code about 10 times already and I can't find a solution I'm satisfied with :(

It seems if I have two classes, one is just a wrapper for an image with a scale method, and the cache is a singleton with a bunch of static methods, in that in ends up looking like what I already have except with another layer of abstraction (the CoverArtImage class).

Perhaps you could show me skeleton classes or UML design that would work better?