goHamlib
goHamlib copied to clipboard
roadmap
Hi,
fair enough :-) So far I have completed 80% of the bindings. A few bindings, in particular related to not so frequently used features like Channel Memory and CTCSS are still missing.
The current release status should be considered alpha and changes along the way will still happen.
I want to provide some overloading functions to simplify the usage. Instead of working with enums, I think in most cases it will be easier to offer an alternative for string usage. So instead of using goHamlib.RIG_VFO_A one could use in the future just "VFOA".
Does this help?
@dh1tw I submitted a PR, but wanted to know if you were open to me making some more go'ish changes related to the constants. Namely creating types for each set of constants and changing the names (e.g. RIG_DEBUG_NONE => DebugNone)
Hey Todd, thanks for your PR! I just reviewed it and I like your changes! I will comment on a few things directly in your PR #2.
I like your idea to move to a more go'ish API. We just should make sure that we are consistent with the naming. PRs are more than welcome!
BR Tobias