LeaderPivot VS fast

I have been trying to reduce the memory footprint on this guy (https://github.com/leaderanalytics/LeaderPivot) for a couple weeks and have not moved the needle one bit (literally). If you could give me shove in the right direction I would appreciate it greatly.

I needed an open source pivot control for an app I'm working on. Couldn't find one anywhere so I wrote one. The control has a base logic component that is responsible for loading data and building the node and matrix structures that are necessary to build the UI. Each UI implementation renders the control based on these structures.

Couple months ago I posted a link to LeaderPivot, a base library I write for building a pivot grid. I also posted LeaderPivot.Blazor which is a Blazor implementation. Today I am pleased to announce LeaderPivot.XAML.WPF which is an implementation for WPF.

The control consists of two components. The base library does all the data work. It first creates a hierarchical node structure. From that it creates a matrix that has properties a UI will need to render the control. The Blazor implementation is just a wrapper around aforementioned base. Eventually I may write a MAUI version if I find the time to do so.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

If you are generally interested in how to write components that can be used by many frontend libraries (react/vue, etc), you should take a look at https://github.com/microsoft/fast. I was tangentially involved with porting an existing component library to it and the end result was pretty framework agnostic and well made.

Could not have articulated it better, especially when compared to other MS project sites like https://www.fast.design/. Maybe the dev or someone on the team downvoted me :/

I know FAST is not used that much but I wanted to cover it as it seems to be the only library that reflects attributes by default. By default it won't do any type coercion unless you use the mode: "boolean", which works almost like an HTML boolean attribute, except an attribute present but with the value "false" will coerce to a property value of false!

This doesn't mean you are required to write vanilla JavaScript web components either. If you are familiar with using Fast or Lit to write web components you can include those libraries in you Enhance application. However, with the introduction of Enhance base classes for the light and shadow DOM you can get the same DX improvements where you write less boilerplate web component code while enabling the sharing of a render method between the SSR and CSR rendering.

You could take a look at FAST https://www.fast.design/. I know it is not what you asked but ...

FastUI from Microsoft? https://github.com/microsoft/fast

I want to use Fast Components, so I've added the Microsoft.Fast.Components.FluentUI NuGet package and added the relevant CDN script tag to index.html.

fast- (Fast components from Microsoft8)