Qt for WebAssembly

@SimonSchroeder I have been using it internally and it works really well. I went with the single thread approach (without async) as that seems to be the most supported version and for an application that behaves like a website I don't really need threads anyway. There are some things that we need to be careful like not calling code that breaks the Qt event loop like qdialog.exec(). There are also some things that don't work as expected but that I found workarounds for and bug reports have been opened, so they will be fixed in the next versions. https://doc.qt.io/qt-6/wasm.html Is a good place to start reading. Version 6.5.2 seems to work decently well and it will be good to start. You can also check the betas to see how bugs are getting fixed (in case you run into some issue with 6.5.2).

@JonB I am not a lawyer but from my understading of GPL3, if the website is public (used by other people outside of the organization that owns it) the source code (for the frontend) must be made available in case of a request. Otherwise you will need a comercial Qt license to keep it private (and I am not sure if the acquired license from the developer will fulfil this when the developer delivers the website to the customer and the project ends). Edit: Nevermind, I am most likely wrong here, according to here: https://www.qt.io/faq/tag/qt-commercial-licensing "Can I continue to distribute my application after my developer license has expired?" It should be ok if the project ends, and the customer should be able to continue the website without licensing issues, well at least as long they don't modify the source with Qt tools.

@SGaist nevermind!.. i got the way, i needed to copy *.js, *.wasm and *.html to my public_html folder .. thats all. thanks anyway.

I have started a bug report https://bugreports.qt.io/browse/QTBUG-116231 You can follow or comment there.

Finally getting around to digging some more into this, and it seems that the issue is tied to the multi-threaded kit. If I choose the single-threaded WebAssembly kit then everything works fine. Why would the "threadedness" make a difference?

@SGaist Hi, I do remember that they did that split . The tools portion is fairly large by itself, but I am also tempted to look over the IDE as it has been some time. Overall, I am just a Hobby type of programmer & lately I have been playing around in Lua code ~for the dcs online flight sim's missions . I was impressed with the language itself :) Anyhow,not using the Atom IDE lately, so a quick switch to Visual Studio sounds like a plan. Maybe it will install a bunch of it onto the 2nd drive (a SSD) ! Qt 6.4 itself is looking pretty kewl, a lot more features than the last time I programmed in C++ .

Hi and welcome to devnet, If you want to know about the gory details, look at the wasm platform plugin in the qtbase sources.

@dacidi my problem solved using release with debug information instead of debug

@dacidi problem solved using release with debug information instead of debug

@JonB i Will give a try to showEvent and comment Thanks!

@Mesrine I solved the chrome error by only copying the text to the clipboard. It seems that textEdit.copy(); try to copy images also to the clipboard and this still is not supported on some browsers. so I made my own class for text-only copy to clipboard class TextClipboard :public QObject { Q_OBJECT Q_PROPERTY(QString text MEMBER m_text NOTIFY textChanged) QML_ELEMENT public: TextClipboard(QObject *parent = nullptr):QObject(parent),m_text(QString()),clipboard(QGuiApplication::clipboard()) { } Q_INVOKABLE void copy()const { clipboard->setText(m_text); } signals: void textChanged(); public: QString m_text; QClipboard *clipboard; }; In the qml file where the text has to be copied on click on a Image I set TextClipboard { id:tclip text:root.address } Image { id:img anchors.centerIn:parent sourceSize.width: root.width-10 source: "image://qrcodeblack/"+root.address MouseArea { anchors.fill: img onClicked: { tclip.copy(); } } } And this solves the error

Nevermind, this error shows when nullptr reference is being used.. thanks anyway.

@JasonWong probably that was the problem, Qt version.. i haven´t tested on 6.5.2, so i go through there.. thanks.

@JasonWong Thank you, that's promising. Apparently it misses the meta to allow cross origin requests so I couldn't test it with another file, but it's nice to know that it is possible even if I'm unsure that I could code using OpenGL that is far beyond my skills.

This was solved with DayOfWeekRow, MonthGrid, and related new components in Qt6.