Is Qt render alive?

[catap]

Is Qt render alive?

[jmercouris]

Qt render is effectively dead, we are hard at work on a cl-electron port if you would be so inclined as to help :-)

[catap]

@jmercouris Presumably that depends on NodeJS?

chromium + node :)

[aadcg]

In that case, I think we should close this issue.

QtWebEngine is rather limiting and once we close #2989 we'll stop supporting it.

@jmercouris, closing?

[jmercouris]

Qt had too many issues for us, that is why we are working on a different version. I wish it were easy, but finding a good renderer is really hard.

[catap]

@jmercouris well.. this seems quite interesting idea to be honest.

Help? I think I may able to help to port it to macOS. I've suceffuly build and run Nyxt-3.5.0 on macOS via MacPorts:

[barracuda156]

Qt render is effectively dead, we are hard at work on a cl-electron port if you would be so inclined as to help :-)

@jmercouris Presumably that depends on NodeJS?

@catap How about fixing NodeJS over a weekend? We just need to rewrite the assembler…

[barracuda156]

@jmercouris Presumably that depends on NodeJS?

chromium + node :)

Oh, so trivial to fix LOL

@jmercouris It is really desirable to have either Qt4 or Carbon backend working.

[aadcg]

@catap if you're able to run Nyxt on macOS using WebKit, what would be the advantage of using Qt? Better performance since it uses Chromium's engine?

[catap]

@aadcg nope, I was just courious about it status because I've tried to build it at begining with Qt and after some time and fixing some "forgotten things"... well I've started to doubt that it works.

[catap]

Right now it simple doesn’t supported 🫣

[aadcg]

Yes, we don't ship Nyxt with Qt since it always lagged behind the WebKit port.

Again, I'm eager to listen to the motivation behind the interest in Qt when #2989 is an on-going effort and the currently widely supported WebKit port provides a better experience.

[barracuda156]

@aadcg There are platforms where WebKit is not there, and fixing it is non-trivial, time-consuming and potentially just impossible. Also, there are infinite number of WebKit-based browsers around.

[aadcg]

@barracuda156 what about QtWebEngine? Doesn't the same argument apply?

Also, there are infinite number of WebKit-based browsers around.

And what conclusion are you extracting from this fact?

[barracuda156]

@aadcg I merely replied to “Again, I'm eager to listen to the motivation behind the interest in Qt”. I won’t convince anyone here, especially if the matter is already decided.

QtWebKit exists back in Qt4, which works fine. Early versions of Qt5 should be fixable with moderate efforts. Fixing V8 requires rewriting assembler to begin with – and then fixing unknown number of bugs, because no one tested it on 32-bit Big-endian for years. So to me there is a difference.

And what conclusion are you extracting from this fact?

I guess it is pretty obvious for anyone to arrive at :) But it is your project, and you can do whatever you wish with it, of course.

[aadcg]

I won’t convince anyone here, especially if the matter is already decided.

Everything is always open to discussion.

I'm sincerely trying to understand your view but I'm afraid I don't get it yet.

Nyxt is developed in such a way that switching web renderer is relatively easy. Let's focus on WebKit-based and Chromium-based renderers. The GUI toolkit is irrelevant here (GTK, Qt, etc). We have a port that works on WebKit. For Chromium we used to support QtWebEngine, but it proved to be rather uninteresting. Our best bet to achieve that goal is to close #2989.

Please share your knowledge and perspective. Thanks!