Thanks -- that article was helpful, even if it didn't really provide a
good answer besides cheat. Silly thing is, there's really no need
for the limitation -- a larger file could easily be compressed/
decompressed in chunks, and still be seamlessly readable as a
sequential file. You probably
In many cases, I/O speeds are slower than decompression speeds. In
these cases, it's actually faster to load/decompress a compressed file
that just loading an uncompressed file. If you really want best
performance, you should profile your flash read speed versus your
decompression speed.
--
You
Regarding compression in raw - you can test this pretty easily by first
adding a large text file into that folder, then a large pre-compressed file
(e.g. cut a portion out of a video file, or use a JPEG) and comparing
resulting .apk sizes...
--
Kostya Vasilyev -- http://kmansoft.wordpress.com
The issue has nothing to do with speed. The issue is getting a large
file to be readable AT ALL. When you open a compressed file larger
than 1M you get an exception: Data exceeds UNCOMPRESS_DATA_MAX
On Sep 29, 2:50 pm, Bret Foreman bret.fore...@gmail.com wrote:
In many cases, I/O speeds are
The issue has nothing to do with speed. The issue is getting a large
file to be readable AT ALL. When you open a compressed file larger
than 1M you get an exception: Data exceeds UNCOMPRESS_DATA_MAX
I called my 3MB .zip file a .jet file to get it to be added to
the .apk uncompressed.
I
5 matches
Mail list logo
