Is this project still being maintained?

[ghost]

No description provided.

[Plaristote]

For lack of time, not really. But for what's already been implemented, it doesn't work half bad. I can provide help, if needed.

[bam80]

Is this still actual or Qt for WebAssembly is a way to go?

[Plaristote]

Well, the project doesn't really get maintenance anymore...

Qt for WebAssembly is very different from QMLWeb. WebAssembly comes with its own set of restrictions, while QMLWeb is pretty much typical web development.

If you want to make Qt applications for the web, Qt for WebAssembly is the way to go.
If you want to make web applications and put some QML in it, then qmlweb is probably better suited for that.

[bam80]

Thank you for the explanation.
The question arises how usable it is if it's unmaintained?
Is it ported to Qt/Qqc 6, etc.?

[Plaristote]

It's pretty usable, when confining yourself to whatever is already implemented.

See, the reason the Qt6 port hasn't been very problematic is just that we don't support that many features from QtQuick... so as far as I remember, the only change needed was to support those import statements which don't specify a version number.

There is one caveat though: due to API changes in the uglify library, I haven't been able to update it, and thus we still lack support for EcmaScript 6.

If you see this project as a way to make web application using QML semantics, then it's definitely usable. We even have additional elements built to help you build DOM document with QML semantics:

import QmlWeb.Dom

DomElement {
  tagName: "section"
  style.backgroundColor: "black"
  style.height: 50
  style.width: 50
  html: "<b>Hello world</b>"
}

If you want to port existing QML application, or depend on the QtQuick.Controls APIs, then we probably haven't implemented enough of Qt/QML to satisfy your needs.