You may have seen the IRC logs,
http://build.nimrod-lang.org/irclogs/07-09-2014.html
someone has done minimal Qt Nim examples already.
But I guess it will be much work to make a full Qt5 wrapper for Nim.
(Fortunately GTK3 is not that hard, but nobody seems to love it. GTK 3.14 is available now, so maybe I will port my 3.12 wrapper to "Nim bigbreak".)
Recently bigbreak got a "mixed mode" code generation so that the files that need it are compiled as C++ while the others remain in C. This should improve interoperability quite a bit. Also c2nim can parse some C++ now. Ofc these features are as stable as anything that nobody uses.
Why does nobody try what we have and report bugs?!
@Stefan We ARE interested in Gtk 3 and want to port Aporia to use it! But we would also appreciate some help.
I have scanned the IRC-logs from time to time... http://build.nimrod-lang.org/irclogs/08-08-2014.html 20:39:29 Joe_knock I don't mind GTK personally, but I've read up on the issues its been having recently 20:48:05 Joe_knock GTK 3 :O Don't use such foul language http://build.nimrod-lang.org/irclogs/25-08-2014.html 17:51:33 BlaXpirit but yes, Qt is the best thing in the world. I see now why people sometimes use GTK+ 17:57:44 dom96 I've used GTK and it's simply not good enough.
I think dom96 is the author of aporia -- it is not my feeling that he is interested in GTK3 for aporia. For me GTK3 is fine on Linux, I generally use it from Ruby currently, and I can not see good reasons to switch to Qt. But of course I know that GTK support is not really good for other operationg systems, GTK developers seems to care not too much about other proprietary operating systems.
Unfortunately I have no small GTK3 application which I could port to Nim -- I have my still unfinished schematics editor written in Ruby, but I have to finish the initial Ruby release before I can consider a port to Nim. And of course I have to learn more about Nim and the changes from Big Break.
I think dom96 is the author of aporia -- it is not my feeling that he is interested in GTK3 for aporia.
Well I talked to him and as I suspected, he is interested in GTK 3 for aporia. As GTK 2 is not maintained anymore it's the natural choice for migration.
Well I talked to him and as I suspected, he is interested in GTK 3 for aporia. As GTK 2 is not maintained anymore it's the natural choice for migration.
OK, then I have a good reason to continue my work on GTK3. But I think I will wait until the "big break" release of Nim is available. Then I will learn the new naming scheme (without the T prefix I guess) and then adapt gdk3, gtk3 and create latest glib, cairo, pango, gtksourceview and others.