Repository navigation
A project manager called Honk and some libs for Goose #236
carabistouflette
started this conversation in
Show and tell
Replies: 1 comment 2 replies
|
We need a better way to list Goose projects, for now on the discord there is also a #projects forum. As for Honk, that seems to have some overlap with the existing build/package system in goose itself? |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I’ve been building libraries and tools for Goose, and I’d like to share them here.
My longer-term goal is to build a game engine in Goose. I don’t want to rush into the engine itself, so I’ve started with smaller libraries and development tools that I hope will also be useful to other Goose projects.
Honk
The main tool is Honk, a project manager for Goose. It supports Git and local dependencies, workspaces, and project commands for building, checking, and packaging code.
It’s still experimental, but I’d be interested in feedback from people trying it on their own projects.
Libraries
I’ve also published 18 libraries:
CLI and configuration
Data formats and text
System utilities
Networking and downloads
Storage and versioning
There’s also goose-check, a command-line tool for checking a program’s output and exit status against fixtures.
Project status
These projects are public under Apache-2.0. Each repository includes usage examples, validation instructions, and documented limitations. Where there are performance results, the benchmark pages explain the workloads, measured versions, and comparison limits.
They’re experimental: platform support varies, some libraries need native dependencies, and APIs may change. Please check each README for the supported compiler revision and setup instructions.
I’ve used Codex to help develop these projects. I’ve also been reviewing the code and documentation myself, and that work is ongoing. I’m responsible for what I publish, and I want to keep improving these projects as I use them.
If you try one, I’d especially appreciate feedback on the API and setup experience. A small example of something awkward, incorrect, or missing would be useful.
Thanks!
All reactions