I wrote my own archive yesterday, and I wonder how easy that was. Using RC4-encryption (see codearchive) and zip-compression (using pub.zlib) I got it up and running in 4 hours (including time to read bmax-sources to understand the way streams and filters work). Making this work in this short time is more a proof of BMax beauty and power than of my programming skills. That's the reason I love coding in Max, it's fun.
Basically it does the following:
* pack files into a single archive, compressing and encoding them
* install a filter to allow usage in any url-parameter, like LoadImage ("archive::picture.png").
When BMax wants the file as a stream, I read it into a bank, decode it, unzip it and throw a bankstream back.
But, like xlsior said: when it's in memory, everything is a plain bitmap, so it can be ripped theoretically. I just want to keep it all in one file and prevent the average user from ripping out musics and images.
Jake
PS: Leave me a mail if you got questions or want some code
Basically it does the following:
* pack files into a single archive, compressing and encoding them
* install a filter to allow usage in any url-parameter, like LoadImage ("archive::picture.png").
When BMax wants the file as a stream, I read it into a bank, decode it, unzip it and throw a bankstream back.
But, like xlsior said: when it's in memory, everything is a plain bitmap, so it can be ripped theoretically. I just want to keep it all in one file and prevent the average user from ripping out musics and images.
Jake
PS: Leave me a mail if you got questions or want some code