06-02-2008, 12:20 AM
What I wrote is a start for some stuff you could do to compress the data and I thought I made that pretty clear. You obviously don't have to do it my way. I provided an explanation along with code to go with it - I'm not sure what else I could give you. I don't think you really understand how things work with this case of data compression. Theres not really a "pro" or "con" to anything. It either results in smaller data or it doesn't. Only cons I can think of would be time and complexity and those should be pretty obvious just by looking at it. Theres not "method one" and "method two" and you get to decide which one you want to use, theres just hundreds of different techniques ranging in all sorts of depths and complexities and you have to mash them together to find out which would be optimal.
Why do people say just "use binary instead"? Maybe because of the assumption that if you can't write out the binary yourself, or be able to ask specific questions on what you need help with instead of just "how do I make this data smaller?", its probably beyond your level already.
Why do people say just "use binary instead"? Maybe because of the assumption that if you can't write out the binary yourself, or be able to ask specific questions on what you need help with instead of just "how do I make this data smaller?", its probably beyond your level already.