Can .webp also be allowed in the Sao image widget?
What would be the point?
WebP is still no so widely supported as JPEG and PNG. Also it is still difficult for user to manage them as it is only recently that some editing software started to support it.
Also Pillow supports of WebP is conditional to having libwebp installed while jpeg is always available.
I can see there could be interest in serving the images from product_image as WebP on demand for web shop site for example. But usually such image will be served behind a CDN which will perform the conversion.
I think webp is widely used in web nowadays (WebP image format | Can I use... Support tables for HTML5, CSS3, etc) for performance and for the possibility of transparent backgrounds that JPEG does not support.
So for me it makes a lot of sense that Tryton allows the user to use that format (we’re not forcing them!).
I see that there’s been a plugin for gimp for at least 10 years, so it’s probably one of the most recent formats but not really rare at all.
But for me the question is: why should we prevent our users from using this file format?
3 Likes
Yes. webp is extensively used on web sites now, and the reason I asked the question is that it’s a management issue internally. We currently have an Ecommerce site with over 1000 items, many with multiple images. We use webp for the size and transparent background benefits. Since we already have all those images in webp format, we could use them in Tryton without a change to a supported format. Basically, we want to avoid internal duplication of effort, storage, etc.
For image manipulation and webp creation, we currently use Pixelmator Pro on a Mac. An excellent and far less expensive option compared to Photoshop.