u/mladenmacanovic

Blazorise 2.3 released
▲ 26 r/Blazor+1 crossposts

Blazorise 2.3 released

Hello everyone,

Blazorise 2.3 is out.

For those who don't know it, Blazorise is a UI component library for Blazor that works with Bootstrap, Tailwind, Fluent UI, Material, and other CSS frameworks.

Initially, this release was supposed to be fairly small. If anyone remembers, in one of my previous posts I asked whether it makes more sense to have smaller releases with faster cycles, or bigger releases with slower cycles.

I wanted the faster release cycle.

Yeah... didn't quite go as planned.

I wanted to build a Reporting component. But once I started working on the report designer, I found that we were missing several things in the framework.

Instead of building them only for Reporting, we made them standalone components. That's how we ended up with DockLayout, ContextMenu, PropertyGrid, and a new PDF generation extension.

We also added CodeEditor and Resizer, Gantt milestones and weekly timelines, Scheduler improvements, and completely rebuilt DatePicker and TimePicker with Blazor and C#, removing the Flatpickr dependency.

So yeah, it turned into a much bigger release than originally planned.

Release notes: https://blazorise.com/news/release-notes/230

If you use Blazor, I'd be interested to hear what you think, especially about Reporting and CodeEditor.

PS. The default Reddit post editor is really bad. I hate it. PPS. Post edited with Grammarly because reasons.

u/mladenmacanovic — 5 days ago
▲ 2 r/dotnet

What do you think about release cycles?

I've been thinking about how we do releases for Blazorise and wanted to get some honest feedback from the community.

Right now we usually spend a few months working on a release and then ship multiple features and improvements together.

Lately I've been wondering if it would make more sense to release more often instead. For example, instead of waiting until several features are ready, we could release a new version whenever a major feature is finished. So 2.3 would be one big feature, 2.4 another one, and so on.

The main reason I'm thinking about this is that features would get into your hands faster. We wouldn't have to hold back finished work while waiting for the rest of a larger release to come together.

At the same time, I can also see the argument for fewer releases that contain more value in each update.

So I'm curious: what would you prefer as a user of Blazorise? More frequent releases focused on a single feature, or fewer releases with multiple features bundled together?

I'm genuinely interested in hearing different opinions before we decide if this is something worth trying.

reddit.com
u/mladenmacanovic — 3 months ago
▲ 28 r/Blazor+1 crossposts

Blazorise 2.2 is now available

Hello everyone.

Last week, I shared the preview of the Blazorise SVG Charts component, and as I mentioned previously, the release will be done soon. So here it is.

For those of you unfamiliar, Blazorise is one of the oldest Blazor UI component libraries, with the ability to work with CSS frameworks like Bootstrap, Material 3, Tailwind, etc.

The biggest additions in this release are SVG Charts, a fully integrated On-Screen Keyboard, and PivotGrid. The PivotGrid, in particular, took much longer than expected to finish. Especially since I wanted to keep fully C# based and as little JS as possible. That was a success. With SvgChart, I had the same goal but not as successfully. The only thing I had to use JS for was the animation part. That was impossible with only C#. I can live with it, hopefully...

Other components also had a longer than planned development. For example, the new Gestures component led to swipe support in Carousel, which led to limitations in the Animate component, and that eventually resulted in a much better animation system than originally planned.

Anyone who is familiar with our work will notice an updated blazorise.com web and docs. The blog and news sections are now merged into the blog only. The docs sidebar is now fully Bootstrap5 native and looks much cleaner than before. The sidebar is also restructured to make larger components easier to navigate.

There are also plenty of smaller features like the Barcode component, TreeView drag-and-drop support, form validation warnings, and some more.

For a full release notes, it is best to read it at https://blazorise.com/news/release-notes/220

TLDR: New SvgChart, PivotGrid, OnScreenKeyboard, Barcode, update website and docs.

u/mladenmacanovic — 2 months ago
▲ 12 r/Blazor+2 crossposts

New Svg Charts for Blazorise

First things first. This is a shameless promotion post.

In a few more days, specifically on Thursday of next week, we are planning to release Blazorise 2.2 with all the newest features, but before then, I wanted to share our latest work that I belive will be of interest to general public. Our latest SvgChart component(s). Anyone familiar with Blazorise is probably aware that we had Charts for some time, but they were based on the chart.js library. It was done years ago when Blazor was still lacking in SVG support, so we didn't have anything better to do. So we did a Blazor wrapper around chart.js. Not ideal but it works.

The new SVG charts are almost 100% C# code, with a small part of JS needed for animations to work. Oh well. We already support all the same chart types as before(bar, line, radar, etc.), including live streaming, annotations, data labels, etc.

One thing I find nice is the plugin-based system. It can be used to create custom chart types and modify the rendering of existing charts. It will be interesting to see how our users will use it in the future.

Anyhow, the charts can be seen on our preview website at: https://preview.blazorise.com/docs/extensions/svg-chart

Hope you like.

Hope I don't get banned.

u/mladenmacanovic — 3 months ago

Local LLM as Codex alternative

First thing I must say I'm not an expert, but I'm curious if this is possible.

At the moment I'm using Codex on a daily basis. Mainly doing .NET and C#. It's great, I love it.

But, we all know it will not go like that forever.

So, let's say I want to replace Codex with my own setup. How would that work? What GPUs, and how many of them is needed? What model to choose as an alternative? How to train it?

Is there a specialized AI machine instead of GPUs?

There are many questions. I could ask AI but I think it is better to ask someone who knows it first hand...

Edit*. The idea is for it to be on par with codex 5.5 high. If this is even possible.

reddit.com
u/mladenmacanovic — 3 months ago