search

therecipe / qt

Qt binding for Go (Golang) with support for Windows / macOS / Linux / FreeBSD / Android / iOS / Sailfish OS / Raspberry Pi / AsteroidOS / Ubuntu Touch / JavaScript / WebAssembly
GNU Lesser General Public License v3.0
10.5k stars 748 forks source link

Is the project still alive ? #1263

Open Inocla opened 2 years ago

Inocla commented 2 years ago

there wasn't any commit since a long time and this would make me sad if the project was deprecated cuz it's one of the most advanced not web based go ui lib

ghost commented 2 years ago

Maybe someone should fork it. The author hasn't committed anything since Sep 2020. Sus

slatelayer commented 2 years ago

I wish The Qt Company would adopt it, or start a new one. (Does anybody know someone to nudge about it?)

I was using this for my project, but decided to drop it and build a (mostly) pure QML implementation of my interface, a pure Go program, and connect them with a websocket bridge. (I used websockets and JSON since they're available in QML already, and later I might add Mangos/Nanomsg and CBOR.)

This feels like an improvement in some ways: it eliminates a lot of unmaintained (and unsafe) binding code, allows me to update to Qt6, dramatically speeds up builds, and forces a well-defined boundary between the UI and the core. (Going well so far...)

IPC makes sense for my project since I'm running the core as a foreground service on Android anyway. I just decided to always run the core separately on all platforms. It's cool because they can restart each other, so backend updates can be very smooth or even invisible.

Another thing I considered was binding only to Qt Remote Objects, or implementing a pure Go Qt 'remoting' package using its protocol. But honestly I don't know how long it would take, or what it would be like to work with.

@therecipe, I hope you're okay, buddy. Let us know!

------- Original Message ------- On Friday, April 15th, 2022 at 3:15 AM, Aitor @.***> wrote:

Maybe someone should fork it

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>