6 ms·
Anyone had chance to try this yet? Is it any good? I notice the Linux APIs call GTK which, while I can understand the logic of, I rather liked the Qt Go Bindin
by laumars 12y ago
Anyone had chance to try this yet? Is it any good?
I notice the Linux APIs call GTK which, while I can understand the logic of, I rather liked the Qt Go Bindings I played around with last year.
- fit2rule 12y agoIt is very rudimentary; all the basics are there, but there are some glaring things I couldn't figure out yet - like how to move the Window to a new screen position, things like that. Might be my ignorance though, I've only had 15 minutes of glance at it, and as I'm mostly interested in learning Go casually, maybe there's some things I've missed ..
- laumars 12y agoFair play. This is as good a project to learn Go with as any :)
- sparkie 12y agoIt may have been done with Wayland in mind, where there is no client-side way of setting the window position, or even querying it, since wayland does not let the client know. The position of windows is managed entirely by the wayland server.
- andlabs 12y agoWhile I do have Wayland in mind, that's specifically for what I can do with the GTK+ backend when running against GTK+'s limits. For this particular feature, there's a different rationale, but I can't remember what it was right now. That being said, I may add such a thing in the future (there's something in futureplans.md about centering the window right now, so...). And yes, this is still rather incomplete (I'm surprised it's getting so much attention this early!); please feel free to make suggestions!
- sagichmal 12y agoWith the caveats that I haven't used it yet, and that I don't know if it reflects actual product quality: after a skim, I can say the code itself is pretty messy. Randomly formatted, nonidiomatic naming conventions, lots of commented-out blocks and dead code, haphazardly organized.
- andlabs 12y agoWhat random formatting do you mean, other than what go fmt would produce? What unidiomatic naming conventions? I thought I removed all the dead code... which ones do you still see? What suggestions can you make about organization?
- DigitalJack 12y agolines 9-16 of this file: https://github.com/andlabs/ui/blob/master/checkbox.go https://github.com/andlabs/ui/blob/master/checkbox.go or lines 10-12 of this file: https://github.com/andlabs/ui/blob/master/area_darwin.go https://github.com/andlabs/ui/blob/master/area_darwin.go those were the first to files I picked. I have no comment on organization--something I struggle with.
- andlabs 12y agoAre you sure the code in checkbox.go is commented out? That's not what I see. As for area_darwin.go, though it's a comment, it's actually C code being sent to an FFI: http://tip.golang.org/cmd/cgo/ http://tip.golang.org/cmd/cgo/
- marcus_holmes 12y agoDon't sweat it too much. The first thing that happens whenever anyone publishes any Go code on the internet is a random commenter pops up and criticises it for being "unidiomatic". I'm beginning to think that "idiomatic" is actually a portmanteau of "automatic" and "idiotic" because it's such a knee-jerk reaction in the community now. If it's flaws in your variable naming and indentation, let it slide. If it's flaws in the logic or functionality, deal with it.