MudBlazor VS nodegui

Our website is updated as well: MudBlazor - Blazor Component Library

Though I can't develop beautiful UI and good UX even if my life depended on it. I can write a functional front-end, but don't expect it to be pretty. I usually ask for assistance regarding that from our UX designers instead where they essentially layout the whole UI (either on figma or Photoshop) so I just need to make it functional. Component based frameworks these days (JS, and Blazor) really helps at least. The UX guys usually make sharable base components that the company needs (buttons, grids, etc...), which includes all the styling and animations and we use those instead to create decent looking UI. For personal stuff I use MudBlazor which kinda does the same, but I do know a bit of css to customize when needed.

There are a ton of component libraries out there. I like the mudblazor library. https://mudblazor.com

There are grid controls from the usual commercial vendors like Radzen and Telerik. I used them briefly during a free trial. It has a funny name, but MudBlazor [1] has been the MIT licensed library I have been using lately. I have been using their Table control, which may be what you are looking for in a data grid. [2] Check it out and see.

[1] https://mudblazor.com/

[2] https://mudblazor.com/components/table#api

It seems to be a known issue a known issue. By default, external libraries such as MudBlazor are not trimmed

I recommend Mud blazor if you're going for Material design. For other design languages Andt Blazor's pretty polished and there's Blazorise as well if you want to be flexible (it supports Antd, Bulma, Bootstrap and Material via configuration).

The ones I've used that's pretty good are MudBlazor (Material Design), Antd blazor (Antd), and Blazorise (Multi design support via configuration). There's also the newly announced Fluent UI for Blazor at MS build that's from MS themselves but I haven't tried it yet.

There's Uno that's been talked about by MS community standups if you wanna use UWP XAML to do the Job. If you wanted to use Blazor though, you'll have to at least learn a bit of CSS and Html. Luckily you can find really nice component libraries like mudblazor that does a lot of the nitty gritty html + styling for you. So you'll just have to use their components most of the time and with little to no JS required (depending in your usecase).

This looks like it hasn't been maintained in years but there's a modern equivalent in NodeGUI [1] which also has React/Svelte/Vue implementations. Unfortunately it requires a custom build of Node that merges the libuv and Qt6 event loops so YMMV.

It actually inspired me to write my own implementation with Svelte on top of QuickJS and Qt Widgets but the task of wrapping the entire Qt6 API in Rust proved to be intractable once I found out that most methods weren't marked Q_INVOKABLE and thus couldn't be called via reflection (requiring manual wrapping). Providing a `Document.createElement` API that created Qt Widgets with working attributes and event handling worked surprisingly well though!

[1] https://github.com/nodegui/nodegui

Hi, so this NodeGui library for building apps with native components is something I really want to get into, but, it does not work for me.. so I am starting this thread to check with yous (I depleted google results) if any one of you have tips or workarounds I can use. I wish to build a desktop app, but I really do not want to bundle a web browser for that purpose and NodeGui seems perfect.

Use NodeGui (or some equivalent tool) for this. Source: https://docs.nodegui.org/ This is needed because this entire project will run natively, by that I mean it will run with no browser, no local host and it no internet connection.

NodeGUI

Let's continue exploring Electron alternatives. This time, NodeGui. NodeGui uses Qt5 instead of Chromium, so we'll be leaving the familiar web development behind, but it tries to not be too far from it, as web development is what everyone knows.

(Disclaimer: My knowledge of Rust very limited, but I have quite a bit of experience with getting Qt/KDE classes to work with other languages.)

You are absolutely right. The effort to be acceptable bindings for Qt would be a tiny fraction of the cost compared to building a whole new Rust native GUI library.

Qt is huge set of libraries with an equally huge API. But there are a lot of shortcuts and smart ways of approaching the problem to get what you want out of Qt for minimum effort.

Bindings like PyQt and even PySide go for the nuclear option of generating bindings for the whole Qt API and trying to match the C++ API in style too. This is an absolutely massive huge task. Also, getting people to contribute to an open source bindings project is hard. Getting people to contribute to a bindings generator is even harder.

NodeGui https://github.com/nodegui/nodegui, Qt bindings for Nodejs, on the other hand takes a very different approach which in one way is low-tech but I think is actually very smart. I'll summerise the differences:

* It focuses on Qt Widgets first. This greatly reduces the amount of work to the parts that people actually need. (BTW, if you just want QML and Rust back-end then Jos van den Oever's work at https://invent.kde.org/sdk/rust-qt-binding-generator has probably got you covered already.)

There is actually a new GUI framework based out of Qt (a C++ GUI framework) that I have found recently : https://docs.nodegui.org/