Portable print composition
Pagination & Preview
Make page structure and preview independent from the eventual printer backend.
Explore source ↗Capability
Documents become page sequences through standard, N-up, booklet, or poster layout, then feed reusable Avalonia page setup and preview windows before submission.
- 01
Standard, N-up, booklet, and poster layout
- 02
Page setup and preview models
- 03
Avalonia preview windows
- 04
Vector-aware deterministic pagination
How it composes
From intent
to working system.
Capture
A visual or document becomes a portable print document.
Paginate
Ticket and layout rules resolve page boundaries and placement.
Preview
Reusable UI presents pages, options, and navigation.
Commit
The same session proceeds to export or platform submission.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet add package PrintingTools.Coredotnet add package PrintingTools.UI<PackageReference Include="PrintingTools.Core" Version="VERSION" /><PackageVersion Include="PrintingTools.Core" Version="VERSION" />var request = new PrintRequest(PrintDocument.FromVisual(report)){ Ticket = PrintTicketModel.CreateDefault(), Description = "Quarterly report"};var session = await manager.RequestSessionAsync(request);var preview = await manager.CreatePreviewAsync(session);Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.