ImageSharp v1.0.0-beta5 Release Notes
Release Date: 2018-08-05 // over 5 years ago-
💥 Breaking changes
🚚 All processing extension methods have been moved to the
SixLabors.ImageSharp.Processing
namespace to improve API discoverability for vanilla VS and VS Code users. (#645) Sub namespaces likeSixLabors.ImageSharp.Processing.Transforms
do no longer exist! You have to remove these using statements from your code:using SixLabors.ImageSharp;using SixLabors.ImageSharp.PixelFormats;using SixLabors.ImageSharp.Processing; // The only namespace required for processing extensions!u̶s̶i̶n̶g̶ ̶S̶i̶x̶L̶a̶b̶o̶r̶s̶.̶I̶m̶a̶g̶e̶S̶h̶a̶r̶p̶.̶P̶r̶o̶c̶e̶s̶s̶i̶n̶g̶.̶T̶r̶a̶n̶s̶f̶o̶r̶m̶s̶;̶ // COMPILATION ERROR!
🚚
image.SavePixelData()
APIs have been removed in favour ofimage.GetPixelSpan()
(#628)🔧
Configuration.ParallelOptions
has been replaced withConfiguration.MaxDegreeOfParallelism
(#667)
👌 Improvements since beta 4:
- 🛠 Fixed all remaining issues with .NET Core 2.1
- Jpeg improvements:
- 📇 Introduce
PixelResolutionUnit
inImageMetaData
, fix #490 (#649) - PNG improvements
- ⚡️ Optimized font rendering by caching glyphs (#614)
- 👌 Improved Gif and Quantization performance when using diffusion by
~600%
(#637) - Cross target .NET Core 2.1 (#604)
- Histogram Equalization (#644)
- Deeper
System.Memory
API integration:- Span overloads for
Image.Load()
andImage.DetectFormat()
(#618) image.GetPixelSpan()
andimage.GetPixelRowSpan()
extension methods for fast pixel data manipulation (#607)Image.WrapMemory(...)
for native interop use-cases (#660)- The
MemoryAllocator
API is now public and shared across all SixLabors projects (#665)
- Span overloads for
NuGet
📦 https://www.nuget.org/packages/SixLabors.ImageSharp/1.0.0-beta0005
📦 https://www.nuget.org/packages/SixLabors.ImageSharp.Drawing/1.0.0-beta0005