You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I'd like to propose adding WebP support for CPP targets in Lime.
WebP is an amazing image format that offers significant advantages: smaller file sizes compared to PNG and JPEG, support for both lossless and lossy compression, and excellent quality preservation. It’s widely used across the web to save bandwidth and reduce load times, and its benefits make it a great choice for modern applications.
Currently, Lime supports WebP only for HTML5 targets, which is great for web projects. However, it would be fantastic to have WebP support extended to CPP targets (Android, iOS, Windows, macOS) as well. From what I understand, there are no significant technical barriers to implementing this — it just needs to be done!
In my case, my project is built entirely around WebP assets for HTML5, and introducing a separate set of assets for CPP builds would be extremely inconvenient and inefficient. Expanding WebP support across all platforms would greatly simplify workflows and ensure consistency for developers relying on this format.
Would love to hear the community's thoughts and whether this can be considered for future updates to Lime.
Thanks!
The text was updated successfully, but these errors were encountered:
Hello! I'd like to propose adding WebP support for CPP targets in Lime.
WebP is an amazing image format that offers significant advantages: smaller file sizes compared to PNG and JPEG, support for both lossless and lossy compression, and excellent quality preservation. It’s widely used across the web to save bandwidth and reduce load times, and its benefits make it a great choice for modern applications.
Currently, Lime supports WebP only for HTML5 targets, which is great for web projects. However, it would be fantastic to have WebP support extended to CPP targets (Android, iOS, Windows, macOS) as well. From what I understand, there are no significant technical barriers to implementing this — it just needs to be done!
In my case, my project is built entirely around WebP assets for HTML5, and introducing a separate set of assets for CPP builds would be extremely inconvenient and inefficient. Expanding WebP support across all platforms would greatly simplify workflows and ensure consistency for developers relying on this format.
Would love to hear the community's thoughts and whether this can be considered for future updates to Lime.
Thanks!
The text was updated successfully, but these errors were encountered: