Developing a better compression system for the .fset files

[kalwalt]

I already posted this question in the NFT-Marker-Creator issue tracker. To keep tracks and find resources, solutions or anything else.

[kalwalt]

@nicolocarpignoli @Carnaux @ThorstenBux i think we could try to compress the files with https://github.com/kripken/lzma.js (it use LZMA compression algorithm) maybe packaged all together and then de-compressed inside jsartoolkit5? Do you think that it worth the try?

[ThorstenBux]

@kalwalt great idea. I was thinking about something like that but haven't started yet to look into possible options. Having that includes into jsartoolkit makes total sense to me.

[kalwalt]

So do you think that it could be a good idea? i know that artoolkit5 has zip.c inside ARUtil but i think that the LZMA has a better compression. I will start with this library instead. I will see what i can do!

[ThorstenBux]

Yes good idea for sure.
Two things,
1 yes zip.c is included but I think what we can handle in JS is preferred to using c/wasm code.
2 Browsers might be handling decompress zipped artifacts automatically. That is one thing to consider before looking into doing it manually.

[kalwalt]

Yes good idea for sure.

ok! 😄

Browsers might be handling decompress zipped artifacts automatically. That is one thing to consider before looking into doing it manually.

So doesn't it needed to decompress them? or are you saying that can be an issue?

[ThorstenBux]

Yes good idea for sure.

ok! 😄

Browsers might be handling decompress zipped artifacts automatically. That is one thing to consider before looking into doing it manually.

So doesn't it needed to decompress them? or are you saying that can be an issue?

Saying the browser can potentially decompress them automatically which is a great feature and could save you some work.

[kalwalt]

Yes good idea for sure.

ok! smile

Browsers might be handling decompress zipped artifacts automatically. That is one thing to consider before looking into doing it manually.

So doesn't it needed to decompress them? or are you saying that can be an issue?

Saying the browser can potentially decompress them automatically which is a great feature and could save you some work.

i understood now, thank you!

[ThorstenBux]

https://stackoverflow.com/questions/32172704/is-gzip-automatically-decompressed-by-browser

[ThorstenBux]

Hi there, how are you.
I looked a bit into that today and found that compressing all artifacts (fset, fset3, iset) into one zip won't work as a browser can't extract one zip into multiple files.
However, what we can do. We can take the content of the artifact and encode them with base64. Then add them to a json like this:

{
 fset: <<base64>>,
fset3: <<base64>>,
iset: <<base64>>
}

And would have in one file which potentially could be zipped.
This would also have the extended benefit to easily add it to ARStudio.
The NFT creator would need to be modified to allow this.