This was supposed to be a relatively small release with a faster release cycle. That didn't quite work out.
The main thing I wanted to build was Reporting with a visual designer. Once I started working on it, I realized we were missing several pieces needed to make the designer work the way I wanted.
Instead of hiding those inside Reporting, we made them standalone components: DockLayout, PropertyGrid, ContextMenu, and PDF generation.
That ended up being the interesting part of the release for me. One feature forced us to fill several gaps in the framework, and those pieces can now be used completely independently of Reporting.
We also ended up rebuilding DatePicker and TimePicker in Blazor/C# and removing the Flatpickr dependency, which had been on my list for quite some time.
Happy to answer technical questions about the report designer, component architecture, or any of the decisions we made.
stsrki•1h ago
This was supposed to be a relatively small release with a faster release cycle. That didn't quite work out.
The main thing I wanted to build was Reporting with a visual designer. Once I started working on it, I realized we were missing several pieces needed to make the designer work the way I wanted.
Instead of hiding those inside Reporting, we made them standalone components: DockLayout, PropertyGrid, ContextMenu, and PDF generation.
That ended up being the interesting part of the release for me. One feature forced us to fill several gaps in the framework, and those pieces can now be used completely independently of Reporting.
We also ended up rebuilding DatePicker and TimePicker in Blazor/C# and removing the Flatpickr dependency, which had been on my list for quite some time.
Happy to answer technical questions about the report designer, component architecture, or any of the decisions we made.