ScottPlot VS library

The pull request from which this code is based on: https://github.com/ScottPlot/ScottPlot/pull/2221

ScottPlot is another .NET option besides OxyPlot and LiveChartsv2. There are a few libs that wrap matplotlib from Python like MatplotlibCS if that's your thing. You could also WebView2 and d3.js for an offline app. It really depends on what you're producing charts for: a highly stylized figure might not be appropriate for an academic publication, interactivity may be important, a very specific type of chart out-of-the-box might be important, etc.

I know you said no 3rd party controls but https://scottplot.net/ is a free and open-source plotting library for .NET which you can use from WPF. The Github page is here https://github.com/ScottPlot/ScottPlot

I dont know what type of visualisations you need but if you are doing a simple WinForms app you cant beat ScottPlot

I was mostly wondering about the charting library itself, in isolation of QuestPDF. ScottPlot is the other one I was considering besides microcharts. Since you mentioned using QuestPDF in production for reporting, I was wondering if perhaps you also used any of the OSS charting libraries in building those reports and if you have any insights you can share. Docs and demos are a good start when picking one, but lived experience is very valuable.

Give the official QuestPDF repository a star ⭐ so more people will know about it. Most developers evaluate project maturity based on the star count so let's help them make the right decision!

There are already a couple of free or paid libraries in the .NET ecosystem that can be used to generate PDF files. The way how QuestPDF differs is simple: instead of relying on an HTML-to-PDF conversion, it implements its own layouting engine that renders the full content using the SkiaSharp library (a Skia port for .NET, used in Chrome, Android, MAUI, etc.).

Hi, can you please elaborate more about your question? Or create a discussion on the repository page? https://github.com/QuestPDF/library/discussions I am not sure exactly what requirement you would like to achieve :)

QuestPDF is my go-to.

Hi :) That is a good point about most of the APIs available. I truly believe that it does not apply to the QuestPDF library. The Fluent API here is used only to describe the document's content, to create new element instances and assign them to parents. In other words, there is no business logic involved in this code area. Please analyze the QuestPDF.Fluent namespace. You will find that most of the API invocations are super simple and straightforward.

check out https://github.com/questpdf/library