Different Asset Cache destination based on scripts included about asset_compress HOT 6 CLOSED

I've thought about instead of 'default' as the default build file, it uses the slugged version of all the included file basenames appended together. This would do much of what you wanted, and fix issues where people use the plugin without planning build files, and getting confusing results.

from asset_compress.

sure, either way... though i've got a bunch of awkward file names, haven;t played with the sproketsy JS requirements yet

from asset_compress.

Slugging the files should just result in a long filename, which isn't that much different than an MD5.

from asset_compress.

I've added a new slug-branch for this feature, so far I've added the filename slugging in 85aac62. I could see the filenames getting a bit silly long though. Perhaps hashing the files would be better?

from asset_compress.

Hashing is what I chose because the slugged filenames (which was my first instinct) were pretty long and I decided that I really wasn't going to be looking at the filenames much anyway...

from asset_compress.

I agree that the hashes would be better, and I've implemented them in 25c8525.

Thanks for the ideas :)

from asset_compress.