-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interest in updates and new features? #24
Comments
Hi @roblillack! Happy to hear this old project is still useful to someone. It was really just something I made for fun but as you see I'm not actively maintaining it by any means, but I'm quite available on GitHub. I'd love for you to upstream the changes. I'll have a look through what you've done during the day. |
That's great to hear! Biggest hurdle will be the "flipped view" addition, IMHO. I need to make sure to have a "traditional" coordinate system (y=0 is the top of the window), don't know how to best make this an option and if it should be exposed as a flag or maybe a build tag. |
Contrary to my former belief (as expressed in the README of my gocoa fork[1] and mojbro/gocoa#24), going forward I think that maintaining gocoa as a separate Go module is too much of a burden as I'm holding back lots of small things which would need Spot-specific code right now. Honestly, most of my existing changes should have been broader to make sense for a general purpose Cocoa binding. To make things a bit easier for me, I decided to import the binding completely into Spot as an internal package. I'll be removing anything that I don't seem necessary for Spot but I will keep the original history to correctly attribute the work done by @mojbro, @phaus, @StarHack, and @dim13 [1] https://github.com/roblillack/gocoa?tab=readme-ov-file#what-is-this
Hey @mojbro, it's been a few years since this repo saw the last update. It was necessary for me to create a fork in order to use gocoa as a backend for Spot, a small cross-platform GUI toolkit I'm working on. Are you interesting in upstreaming the existing (and future) changes, or should I keep it separate? I'll try to keep an up-to-date list in the README of the fork, currently it lists only these changes:
The text was updated successfully, but these errors were encountered: