Actual name and wiki entry

[ShalokShalom]

The actual name of this binding is simply "qt"? I am asking since i write the entry in Qts own Wiki for it.
I am wondering its not there yet..

[therecipe]

Hey

The actual name of this binding is simply "qt"?

Yeah, actually it's nameless.
I wasn't able to come up with something I liked and the obvious ones like "goqt" or "qtgo" were already taken, so I just called the repo "qt" and moved on. So yeah "qt" is the official name, I guess.

I am asking since i write the entry in Qts own Wiki for it.
I am wondering its not there yet..

I'm not sure, I did know that Qt had a wiki but I thought that it was inactive.
However, I would be happy if this binding would be listed there :)

[ShalokShalom]

I think it IS inactive. ;)

I add qt to this list, no acceptance yet, while Ruby and Perl, both with Qt1 until Qt4 support are still in and two other bindings are also added. https://wiki.qt.io/Language_Bindings

Maybe i ping an admin later, no reaction on Qt either yet.

[ShalokShalom]

CuteGo
QuteGo

GoCute
GoQute

[joeblew99]

Nice name :) needs some name that sticks in people's minds

[masiulaniec]

Please don't invent cute names. The ruby world is infested with project names such as "cucumber". One of the benefits of go's hierarchical url-based import path approach is that package names can be simply self-describing. In other words, workarounds from systems using flat namespaces don't apply here.

[masiulaniec]

A related question is whether the current split into large core, gui, widgets, etc., packages is the best possible one. It seems like if all I need is a QLabel, then I should be able to write:

import "github.com/therecipe/qt/QLabel"

... to gain access to the *QLabel.Object type, thus avoiding the cost of compiling&linking 95% of stuff I don't need.

I wonder if this approach was considered but rejected.

[therecipe]

@masiulaniec

A related question is whether the current split into large core, gui, widgets, etc., packages is the best possible one.
I wonder if this approach was considered but rejected.

Yeah, I recall thinking about that when I split the large "qt" pkg from the early days into the modules.
(And also again when the "widgets" module, took 8gb ram to compile)

I think I tried and rejected it because there was a) a lot of duplicate C and Go code necessary to get it working and b) I had problems with circle dependencies.

[ShalokShalom]

@therecipe Any suggestions? I added your project now to the Qt Wiki:
https://wiki.qt.io/Language_Bindings

I think it would be nice to list all the supported Qt library's since some offer 4 of them, others all and so on. You wrote, "Most of Qt's API is accessible from Go."

Is there a specific list?

[therecipe]

@ShalokShalom
Ah, thank you :)

Any suggestions?

Maybe it should be mentioned that you can subclass with the help of qtmoc and thereby extend your "classes" (Go has only structs and no real classes) with custom signals/slots/properties/constructors.
That rcc and {win|mac}deployqt are wrapped by qtrcc and qtdeploy, and that you can simply cross compile to most other targets (>= 10) with the help of docker and vagrant.
And that you can use docker and vagrant for your CI and CD purposes as well.
But there are also a few other things, like the fact that you can re-generate the whole binding with qtsetup against a range of Qt versions. Or that the binding is a one to one mapping against Qt's C++ api. Or maybe even that you don't have to install Qt on your pc at all, if you run the minimal setup with docker. Or that you can override virtual functions (and also signals/slots) at runtime with anonymous functions (Lambdas). And there are probably a few other notable things as well.

But I just took another look to see what has been written for the other bindings, and that was not that much :D
So I'm not sure if you can use my suggestions from above at all.

The only thing that comes close to PyQt's and PySide's docs, tutorials and such.
Is probably the slack channel: https://gophers.slack.com/messages/qt-binding/details
But even I just visit it infrequently.

Also thanks for the name suggestions.
But I'm not really sure if I want to attach a "Go" suffix or prefix at all to it.

Is there a specific list?
Yes, you can find one here:

qt/internal/binding/parser/helper.go

Lines 257 to 311 in 8ca9dc8

	func GetLibs() []string {
	libs := []string{
	"Core",
	"AndroidExtras",
	"Gui",
	"Network",
	"Xml",
	"DBus",
	"Nfc",
	"Script", //depreached (planned) in 5.6
	"Sensors",
	"Positioning",
	"Widgets",
	"Sql",
	"MacExtras",
	"Qml",
	"WebSockets",
	"XmlPatterns",
	"Bluetooth",
	"WebChannel",
	"Svg",
	"Multimedia",
	"Quick",
	"Help",
	"Location",
	"ScriptTools", //depreached (planned) in 5.6
	"UiTools",
	//"X11Extras", //TODO:
	"WinExtras",
	"WebEngine",
	"TestLib",
	"SerialPort",
	"SerialBus",
	"PrintSupport",
	//"PlatformHeaders", //missing imports/guards
	"Designer",
	"Scxml",
	"Gamepad",
	"Purchasing", //GPLv3 & LGPLv3
	"DataVisualization", //GPLv3
	"Charts", //GPLv3
	//"Quick2DRenderer", //GPLv3
	"Speech",
	"QuickControls2",
	"Sailfish",
	"WebView",
	//"NetworkAuth", //TODO:
	"RemoteObjects",
	"WebKit",
	}

And another one would be the list of folders at the root of the repo: https://github.com/therecipe/qt
Each folder (beside "cmd" and "internal") is a Qt module.

[ShalokShalom]

Thanks a lot, that helps me further.

[RadhiFadlillah]

Well, since qt is pronounced kyu-tee, what about :

• gokyu
• goqu
• goku

@masiulaniec I think it's fine if package's name is not self-describing, simply because number of vocabulary is limited while number of libraries or packages will keep growing. Even in Go community there are many packages whose name doesn't describing himself, like gin, martini, cockroach, hugo, etc.

[ShalokShalom]

This repo suggests to name it therecipe-qt: https://github.com/wzwmzm/therecipe-qt/commits/master ;)