Pysar.Blazor
0.1.56
See the version list below for details.
dotnet add package Pysar.Blazor --version 0.1.56
NuGet\Install-Package Pysar.Blazor -Version 0.1.56
<PackageReference Include="Pysar.Blazor" Version="0.1.56" />
<PackageVersion Include="Pysar.Blazor" Version="0.1.56" />
<PackageReference Include="Pysar.Blazor" />
paket add Pysar.Blazor --version 0.1.56
#r "nuget: Pysar.Blazor, 0.1.56"
#:package Pysar.Blazor@0.1.56
#addin nuget:?package=Pysar.Blazor&version=0.1.56
#tool nuget:?package=Pysar.Blazor&version=0.1.56
Pysar.Blazor
Blazor WebAssembly integration for Pysar, a cross-platform
report engine for .NET: the <ReportView> component, printing through the browser, and a
WasmPlatformHandler for file and font access.
Setup
Registration is a service-collection call, and the same renderer serves both the viewer and the exporters — so a custom drawer registered here reaches the screen as well as the PDF:
builder.Services.AddPysar(renderer => renderer.WithDrawer<QRCode>(new QRCodeDrawer()));
The browser has no file system, so assets are fetched up front and held in memory. This is not a preference: fonts are loaded synchronously, and a blocking read on the browser's single thread is a deadlock rather than a stall.
var files = await PreloadedFileSystem.FetchAsync(http, [
"Fonts/Ubuntu-Regular.ttf",
"Images/logo.svg"
]);
WasmPlatformHandler.Install(files);
Showing a report
<ReportView Report="@_report" ZoomMode="@ReportZoomMode.FitWidth" PageSpacing="24" />
The view renders a built report as scrollable, zoomable pages, rasterised one visible tile at a time, so memory follows the size of the viewport rather than the zoom level.
Printing
IReportPrinter resolves to BlazorReportPrinter, which renders the report to PDF off the UI thread
and hands it to the browser's own print dialog. It is registered scoped, because it holds a JS module
reference belonging to one browser context. The report must already have Build() called.
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.AspNetCore.Components.Web (>= 10.0.11)
- Microsoft.Extensions.DependencyInjection (>= 10.0.11)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.11)
- Pysar.Viewer (>= 0.1.56)
- 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
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
## Zoom & gestures
**Trackpad wheel events are now aggregated into a single gesture.**
Wheel events are timestamped and grouped using a new `WheelGestureGap`, and the wheel
anchor in `ReportView` is kept persistent for the duration of the gesture instead of
being recomputed per event.
**Sub-threshold pinch frames are deferred.**
`GestureModel.PinchByStep` / `PinchByScale` now report whether the change actually
reached the `ZoomModel`. Small frames are accumulated and only written once they exceed
`ZoomStepThreshold`. This fixes the visual drift between the model zoom and the rendered
pages during slow pinches.
Added tests covering the accumulation behaviour and confirming that presenter and page
layout do not drift across many sub-threshold frames.
## Internal
- `InternalsVisibleTo` added for the WPF test assembly, enabling direct unit tests of
internal `Pysar.Wpf` logic without widening the public API.
**Full changelog:** v0.1.53...HEAD