Pysar.Viewer
0.1.41
See the version list below for details.
dotnet add package Pysar.Viewer --version 0.1.41
NuGet\Install-Package Pysar.Viewer -Version 0.1.41
<PackageReference Include="Pysar.Viewer" Version="0.1.41" />
<PackageVersion Include="Pysar.Viewer" Version="0.1.41" />
<PackageReference Include="Pysar.Viewer" />
paket add Pysar.Viewer --version 0.1.41
#r "nuget: Pysar.Viewer, 0.1.41"
#:package Pysar.Viewer@0.1.41
#addin nuget:?package=Pysar.Viewer&version=0.1.41
#tool nuget:?package=Pysar.Viewer&version=0.1.41
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.41)
- 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.
## Highlights
### Uno integration: a real entry point
Registering Pysar in an Uno application is now a single call on `Application`, and it works the same
way from every head (WebAssembly, Desktop, Android, iOS, WinAppSDK) — `OnLaunched` is the one place
they all run through.
```csharp
protected override void OnLaunched(LaunchActivatedEventArgs args)
{
this.UsePysar(typeof(App).Assembly, pysar => pysar
.AddFont("Fonts/Ubuntu-Regular.ttf", "Ubuntu")
.AddFont("Fonts/Ubuntu-Bold.ttf", "Ubuntu", FontStyle.Bold));
}
```
- `ApplicationExtensions.UsePysar(...)` and `UsePysarAsync(...)` — the latter preloads
`ms-appx:///` assets for applications that ship them as `Content` rather than `EmbeddedResource`.
- `assetAssembly` is required: on the WebAssembly head the entry assembly is the head project, not
the application project the assets are packaged into.
- Registration moved into `UnoRegistration`; `PysarUno` now exposes `PlatformHandler` /
`ExportService` and resets the export service on re-registration.
### Ctrl+wheel and trackpad pinch zoom the report, not the page (browser head)
`ReportView` has always zoomed on Ctrl+wheel and marked the event handled, but on a browser head
that changed nothing visible: "handled" is a managed routing flag, while page zoom is a DOM default
action that only `preventDefault` on a non-passive listener stops. The reader got a scaled page and
a report that never moved — and the trackpad pinch went with it, since Chrome and Safari deliver it
as a wheel event with `ctrlKey` set.
`UsePysar` now installs a small embedded script, imported from a data URL, so a consuming
application adds one call and no files. Opt out with `suppressBrowserZoom: false` to keep the
browser's own zoom as an accessibility affordance.
Suppression covers the whole Uno canvas: Uno draws the entire application into a single canvas, so
the DOM cannot tell the report from the toolbar beside it. Anything on the page outside that canvas
keeps the browser's zoom.
### Measure probe caching
New `MeasureContext` and `LayoutEngine.ProbeSizeAsync` cache probe measurements, and
`GridLayoutMeasurer` / `StackLayoutMeasurer` now measure through probes instead of re-measuring the
same subtree repeatedly — a large drop in repeat measures on nested layouts.
### A readable diagnostic for the SkiaSharp native/managed split on WebAssembly
An Uno browser head pulls `SkiaSharp.NativeAssets.WebAssembly` through
`Uno.WinUI.Runtime.Skia.WebAssembly.Browser`, which asks for the 3.119 line, while Pysar renders
through 4.151. NuGet resolves one managed SkiaSharp and one native archive, and the two no longer
agree.
Every other platform reports that split as a startup exception with a message of its own.
WebAssembly links the native side statically at build time, so it surfaces instead as a wall of
`wasm-ld: undefined symbol: sk_*` lines naming entry points the application never wrote, with
nothing pointing at the version that caused them.
The check now ships as `buildTransitive`, so it reaches consumers who referenced `Pysar.Uno` or
`Pysar.Blazor` rather than `Pysar` itself — those are the ones who end up on a browser head.
Declaring a dependency on the native package would fix it silently, but it is a 67 MB download
charged to every WPF, console and Uno desktop consumer that will never link a wasm binary.
## Breaking changes
- `PysarUno.Use(...)` and `PysarUno.UseAsync(...)` are removed. Use `Application.UsePysar(...)` /
`UsePysarAsync(...)` instead.
## Other
- Docs updated: root `README.md`, `src/Pysar.Uno/README.md`, `docs/quick-start.md`.
- New `AGENTS.md`; added `opencode.json`.
- Tests: `UnoRegistrationTests`, `MeasureProbeCachingTests`, and a new `PackageLayoutTests`
assertion for the `buildTransitive` payload.
**Full Changelog**: https://github.com/MriyaLab/Pysar/compare/v0.1.38...v0.1.42