Pysar.Viewer
0.1.46
See the version list below for details.
dotnet add package Pysar.Viewer --version 0.1.46
NuGet\Install-Package Pysar.Viewer -Version 0.1.46
<PackageReference Include="Pysar.Viewer" Version="0.1.46" />
<PackageVersion Include="Pysar.Viewer" Version="0.1.46" />
<PackageReference Include="Pysar.Viewer" />
paket add Pysar.Viewer --version 0.1.46
#r "nuget: Pysar.Viewer, 0.1.46"
#:package Pysar.Viewer@0.1.46
#addin nuget:?package=Pysar.Viewer&version=0.1.46
#tool nuget:?package=Pysar.Viewer&version=0.1.46
Pysar.Viewer
Framework-neutral viewer logic for Pysar, a cross-platform
report engine for .NET: page geometry, zoom, tile planning and the tile cache. It depends on the
core Pysar package and is the shared core behind every platform-specific ReportView control.
A built report renders as scrollable, zoomable pages, rasterised one visible tile at a time. Only the visible region is rasterised, so memory follows the size of the viewport rather than the zoom level.
This package is not referenced directly — it arrives transitively with a platform package, which supplies the actual UI control:
| Platform package | Control |
|---|---|
Pysar.Maui |
.NET MAUI ReportView |
Pysar.Avalonia |
Avalonia ReportView |
Pysar.Wpf |
WPF ReportView (Windows only) |
Pysar.Blazor |
Blazor <ReportView> component |
The properties are the same on every platform. PageBorderColor and PageBorderThickness frame each
page, which is what tells a page from the surface behind it when both are light; the line is drawn
outside the paper, so the report itself is never covered by it. PageSpacing is the gap between two
pages, in device independent units — it does not scale with the zoom, so the gap looks the same
however far in the reader is.
A fit mode resolves to a factor only the control knows, so bind EffectiveZoom to show the
percentage: Zoom holds what was asked for, not what the view settled on.
Documentation
License
MIT — see LICENSE.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- HarfBuzzSharp (>= 14.2.1.1)
- HarfBuzzSharp.NativeAssets.Linux (>= 14.2.1.1)
- HarfBuzzSharp.NativeAssets.macOS (>= 14.2.1.1)
- HarfBuzzSharp.NativeAssets.Win32 (>= 14.2.1.1)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.11)
- Pysar (>= 0.1.46)
- SkiaSharp (>= 4.151.2)
- SkiaSharp.NativeAssets.Linux (>= 4.151.2)
- SkiaSharp.NativeAssets.macOS (>= 4.151.2)
- SkiaSharp.NativeAssets.Win32 (>= 4.151.2)
- Svg.Skia (>= 5.2.3)
NuGet packages (5)
Showing the top 5 NuGet packages that depend on Pysar.Viewer:
| Package | Downloads |
|---|---|
|
Pysar.Blazor
A Blazor WebAssembly report viewer for Pysar. |
|
|
Pysar.Wpf
WPF integration for Pysar: application asset access, font registration, scrollable zoomable report view, and printing. |
|
|
Pysar.Maui
.NET MAUI integration for Pysar: application-package asset access, font registration, PDF export and sharing. |
|
|
Pysar.Avalonia
Avalonia integration for Pysar: application asset access, font registration and a scrollable, zoomable report view. |
|
|
Pysar.Uno
Uno Platform integration for Pysar: application asset access, font registration, a scrollable, zoomable report view, PDF printing and sharing. |
GitHub repositories
This package is not used by any popular GitHub repositories.
### Changed
- **Lowered the `Uno.WinUI` floor from 6.7.103 to 6.6.184.** `Pysar.Uno` previously
demanded a version no app on `Uno.Sdk 6.6.42` could satisfy — the Sdk supplies
6.6.184 itself, making the higher floor a hard resolution failure rather than a
warning. `Pysar.Uno` uses no API newer than 6.6, so the floor now matches.
- This is a floor, not a ceiling: consumers on `Uno.Sdk 6.7.30` still resolve
6.7.135, and the Uno sample builds against 6.8.0-dev.159 from its own Sdk.
- `HarfBuzzSharp` remains at 14.2.1.1 — only its outdated rationale comment was
corrected, since `Svg.Skia` (14.2.0), not Uno, is what drives that version now.
### Notes
- Apps blocked on `Uno.WinUI 6.7.103` can now stay on Uno 6.6 — or move to
`Uno.Sdk 6.7.30`, which is published as stable.