I forgot a very important aspect of implementing webP in LiveCode engine. For a first implementation, LiveCode could import (decode) only static -not animated- webP images and exclude the option of exporting images as webP (excluding the encoder from the engine). This would reduce the complexity of this task.
Now, I have to check if these optimized JPG and PNG encoders produce better results with my own test images: https://github.com/google/guetzli/releases https://github.com/google/zopfli https://github.com/subzey/zopfli-png Anyone interested in the topic of image optimization could learn a lot from this webpage too: https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/image-optimization Have a nice weekend! Al _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
