Is there a Native to Qt layer?

Feedback Ideas
1

With all the porting going on, there’s a lot of Gtk, Qt apps. I just wondered, flipping the idea on its head if after writing a native app, there could be headers and a lib to make it a Qt/KDE app (almost).

  1. This would encourage native app development
  2. Qt/KDE would feel like the second option (port)
  3. The APIs being in some sense simpler/more-concise, better for initial development

I remember when the Eclipse Foundation made a Gtk implementation of the AWT, so just an include change made a Gtk Java application. So I kind of had the idea today. I guess the APIs do look good.

Maybe it’s counter intuitive?

EDIT: I remember when Kt used to be wrapper classes around Qt for KDE specifics. In the times of NXPlugin … should Haiku have a man2md? Documentation Formats? (html, md, ...) as html has a lot of surplus tags. Ah Mandrake Linux, blah, blah, …

2

Not Qt/KDE, but have you heard of Cosmoe?

3

Not really what you are asking for, but I have been working on this library for the last year GitHub - gen2brain/iup-go: Cross-platform UI library with native controls · GitHub (still not fully ready for release, almost there). The same app can be compiled for Win32, WinUI3, Cocoa, GTK2, GTK3, GTK4, Qt5, Qt6, FLTK, EFL, GNUStep, Haiku, WebAssembly, Android, and iOS. I guess everything is covered, and I answered the famous “but what is the native UI on Linux” question. Of course, you can use C or C++; there is a nice C++ wrapper that is maintained.

I just shared an app I did here, Comic Book Converter.

4

Yes, code like this exists. In the WIP version of Wonderbrush v3

How well it works, I have no idea. I suspect that removing it may make working on WonderBrush v3 somewhat simpler though…

5

I was thinking something which was more an automated port to Qt when the app is native. It just gives coders options. I’m not sure how easy making a Qt version of all the Haiku objects would be. It’s got a lot of signal/connect stuff. And then just use a different linked shared library(s).

6

I never had to touch any of this while working on Wonderbrush 3. It is completely independant from the other parts.

So you don’t need to remove it, just ignore it.