PanoramicData.Blazor
10.0.454
See the version list below for details.
dotnet add package PanoramicData.Blazor --version 10.0.454
NuGet\Install-Package PanoramicData.Blazor -Version 10.0.454
<PackageReference Include="PanoramicData.Blazor" Version="10.0.454" />
<PackageVersion Include="PanoramicData.Blazor" Version="10.0.454" />
<PackageReference Include="PanoramicData.Blazor" />
paket add PanoramicData.Blazor --version 10.0.454
#r "nuget: PanoramicData.Blazor, 10.0.454"
#:package PanoramicData.Blazor@10.0.454
#addin nuget:?package=PanoramicData.Blazor&version=10.0.454
#tool nuget:?package=PanoramicData.Blazor&version=10.0.454
PanoramicData.Blazor
UI components for Blazor. Try it out on our Demo page!
We needed the following Blazor UI components for several projects, including ReportMagic v3.0:
- Block Overlay
- Table
- Pager
- Tree
- Splitter
- File Explorer
- Context Menu
- Toolbar
- Form
- File Modal
Rather than buying them in, we made our own, Open Sourced them on Github and made them free (both speech and beer).
More will follow, as we need them. However, we are much more excited to see:
- what you need
- your Pull Requests
Please do contribute!
Dependencies
- Bootstrap (a default Library in a new blazor project) >= 5.1.3
Component Documentation
To improve our project's documentation and make it easier to work with our Blazor components, we've introduced a new automated documentation generation process.
What's New?
ComponentDocumentation.md: A new markdown file in the root of the project that provides a comprehensive overview of allPD*Blazor components, including their parameters and descriptions.- Automated Generation: This file is generated by a PowerShell script named
GenerateDocs.ps1. This script scans all components and their parameters, extracting the XML summary comments to build the documentation. - Improved Code Comments: All components have been updated with XML summary comments for their parameters to ensure the generated documentation is as complete as possible.
How to Use It
To update the documentation, simply run the GenerateDocs.ps1 script from a PowerShell terminal in the project root:
.\GenerateDocs.ps1
The script will automatically detect any changes to the documentation and prompt you to commit them. Please note that running this script is currently a manual step required to keep the documentation in sync with the code.
Your Contribution
To ensure the documentation remains complete and accurate, please add XML summary comments to any new components or parameters you create. For example:
/// <summary>
/// A brief description of the parameter.
/// </summary>
[Parameter]
public string MyParameter { get; set; }
This automated process ensures that our documentation stays up-to-date with the codebase, making it easier for everyone to understand how to use our components. It will also help new team members get up to speed more quickly.
Demo Application Documentation
The demo application includes comprehensive documentation for each component, accessible via the Documentation tab on each component's demo page.
Documentation Features
- Three-tab layout: Demo | Source | Documentation
- Interactive examples: Live component demos alongside code
- Progressive complexity: Examples build from basic to advanced
- Deep linking: Direct URLs to specific tabs and sections (e.g.,
/pdtiles?tab=docs#row-curves) - Mobile responsive: Code and demo stack vertically on narrow screens
Creating Documentation for New Components
- Create a
PDComponentDocumentation.razorfile inPages/ - Use the
DocExamplecomponent for each example:
<DocExample Title="Example Title"
AnchorId="unique-anchor"
Code="@_codeString"
Language="razor"
DemoStyle="height: 300px;">
<DemoContent>
</DemoContent>
<Description>
<p>Explanation of the example...</p>
</Description>
</DocExample>
- Add to the demo page:
<DemoSourceView SourceFiles="...">
<DocumentationContent>
<PDComponentDocumentation />
</DocumentationContent>
<ChildContent>
</ChildContent>
</DemoSourceView>
See PDTilesDocumentation.razor for a complete example.
| 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
- BlazorMonaco (>= 3.5.0)
- FluentValidation (>= 12.2.0)
- Humanizer.Core (>= 3.0.10)
- Markdig (>= 1.4.1)
- Microsoft.AspNetCore.Components (>= 10.0.13)
- Microsoft.AspNetCore.Components.Web (>= 10.0.13)
- Microsoft.AspNetCore.WebUtilities (>= 10.0.13)
- PanoramicData.DeepCloner (>= 1.0.8)
- System.Drawing.Common (>= 10.0.13)
- System.Linq.Dynamic.Core (>= 1.7.4)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on PanoramicData.Blazor:
| Package | Downloads |
|---|---|
|
Jakar.Extensions.Blazor
Extensions to aid in development. |
|
|
PanoramicData.Blazor.Demo
Package Description |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 10.0.463 | 0 | 10/30/2026 |
| 10.0.460 | 0 | 10/30/2026 |
| 10.0.457 | 0 | 10/30/2026 |
| 10.0.454 | 0 | 10/30/2026 |
| 10.0.451 | 61 | 10/29/2026 |
| 10.0.435 | 54 | 10/29/2026 |
| 10.0.433 | 49 | 10/29/2026 |
| 10.0.428 | 60 | 10/28/2026 |
| 10.0.424 | 93 | 10/27/2026 |
| 10.0.423 | 88 | 10/27/2026 |
| 10.0.421 | 91 | 10/26/2026 |
| 10.0.420 | 128 | 10/26/2026 |
| 10.0.416 | 88 | 10/26/2026 |
| 10.0.408 | 103 | 10/25/2026 |
| 10.0.398 | 111 | 10/24/2026 |
| 10.0.396 | 137 | 10/22/2026 |
| 10.0.394 | 91 | 10/22/2026 |
| 10.0.388 | 97 | 10/20/2026 |
| 10.0.387 | 87 | 10/20/2026 |
| 10.0.385 | 280 | 10/19/2026 |
- PDMonacoEditor: reloading a page no longer ends the circuit. The editor waits for Monaco to finish loading before it is created, and says so if Monaco never loads. Custom languages and themes are set up before the editor is created, so a custom theme applies from the start. Calls made after the browser has gone no longer throw into the host. New InsertTextAsync inserts at the cursor, and a value set before the editor exists is kept. The border colour follows --pd-monaco-border-color.
- PDStudio: new SetCodeAsync and InsertTextAsync, a ToolbarStartContent slot before Execute (for a File menu), and ShowNewButton. Execute lines up with the editor, separators and borders use quieter colours that suit light and dark themes, and the editor no longer shows a border of its own. New options set tab titles, tooltips and icons, button icons, the Execute tooltip, the results placeholder and how many messages are kept. Only the status icon takes the status colour.
- PDToolbarDropdown: menu items have proper padding and a gap after each icon, so every toolbar menu has more room.