clarify nature of project and relationship with Garmin-Forerunner-610-Extractor
aspiers opened this issue · comments
Tigge/antfs-cli#38 says that this project "holds just the ANT parts (along with some new fixes and an example)" and that the next task is to remove it from the extractor and then use the separate openant repository instead.
But that sounds to me like the extractor code will be left in the Garmin-Forerunner-610-Extractor project, and doesn't that defeat the point of the new naming? Or is the extractor going to be moved somewhere as well? If so, where?
It would be really helpful if this project's README explained the roadmap for this. Currently anyone reading it without deep technical understanding of ANT doesn't have much of a chance to understand what they can use it for (if anything, at this early stage of development).
I'll try to clarify this in the READMEs. For now here is a short overview:
openant will be a library for the ANT, ANT+ and ANT-FS technologies. This can be used to talk with various equipment that uses these technologies (such as scales, hearthrate monitors, training equipment, sport watches, etc).
Garmin-Extractor (soon antfs-cli) is using openant to communicate with some sport watches (that uses ANT-FS) to download and upload files from them, saving them, plugin system etc.
Gotcha - yes, would be very helpful to have that in the READMEs. Thanks!
Please can you also give your thoughts on braiden/python-ant-downloader#59 ? Thanks again!