Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace Image Compression Feature #526

Open
1 of 4 tasks
WillStrohl opened this issue Jan 16, 2025 · 0 comments
Open
1 of 4 tasks

Replace Image Compression Feature #526

WillStrohl opened this issue Jan 16, 2025 · 0 comments
Labels
enhancement estimate exists An estimation and scoping process has already been done. Requires Triage Someone needs to reproduce this issue. sponsors welcome We're looking for one or more people to directly sponsor this update.

Comments

@WillStrohl
Copy link
Member

Sponsorship

If this request requires additional support (e.g., such as direct email/phone/meeting/development), I have the following interest in helping to sponsor the effot via GitHub Sponsors:

  • None, please continute to work for me for free :P
  • Absolutely, I get value out of this!
  • Maybe later
  • I'm already a sponsor... Woot!

Is your feature request related to a problem?

Currently, HCC uses an older method of resizing and compressing product/category images uploaded into the store, known as ImageResizer. Some people have seen image quality issues with this method and may like it to be updated to be something more contemporary.

Describe the solution you'd like

Upendo has already taken the time to research various options that could be used as a newer alternative to ImageResizer and propose replacing this feature with Magik.NET. This is a newer method that not only will create higher-quality images, but it also will broaden support for other image file types, such as SVG.

This update would replace ImageResizer with Magik.NET and support more image file types across HCC. Magik.NET is a widely adopted and supported open-source library who's focus is soley on image compression and resizing.

Describe alternatives you've considered

We researched the best tool to optimize and enhance image quality for the project, considering the potential for an update to the current image processing system. After evaluating several options, we found that ImageSharp was the most suitable choice due to its performance, compatibility with modern formats like WebP, and it's advanced image compression and manipulation capabilities.

However, the latest versions of ImageSharp require .NET 6 or higher, which means it is not compatible with our current DNN environment which limits us to .NET Framework 4.8. Due to this incompatibility, we decided to investigate other alternatives that could meet our requirements in the .NET Framework.

Among the options evaluated, Magick.NET (an adaptation of ImageMagick for .NET) and SkiaSharp proved to be viable choices that meet our image processing needs and are compatible with .NET Framework 4.8. Both libraries offer extensive image manipulation capabilities and are recognized for their performance in .NET environments.

Additional context

An internal estimate has already been created and is ready for a potential sponsor.

@WillStrohl WillStrohl added enhancement sponsors welcome We're looking for one or more people to directly sponsor this update. estimate exists An estimation and scoping process has already been done. Requires Triage Someone needs to reproduce this issue. labels Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement estimate exists An estimation and scoping process has already been done. Requires Triage Someone needs to reproduce this issue. sponsors welcome We're looking for one or more people to directly sponsor this update.
Development

No branches or pull requests

1 participant