nightscout / nightscout/AndroidAPS
[Feature Request] seperate colour schemes for wear aapsclient and wear aapsclient2, changes on filname on build.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 6.4k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 19
Description
Since the wearapk for the AAPSClient and the AAPSClient2 currently have the same filename when bulding in Android Studio, it's not visible on first sight which one is which. To prevent confusion the filename has to be altered beforehand.
Furthermore, the colour scheme of the wearapks for AAPSClient and AAPSClient2 is the same, "blue" for both versions to be exact.
If the wearapks of both Clients are installed on the same watch - as it is in my case, all menue items are blue. It can't be determined which menu button corresponds to which Version of the Client.
Since one can switch between different watchfaces for Client and Client2 it would be great as well, if there would be yellow menue items on the watch for Client and blue menue items for Client2 as well following the usual colour scheme in AAPS.
Thank you
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named; start by locating the Wear AAPSClient and AAPSClient2 build configuration and the menu colour definitions in Android Studio. Done means the two wear APKs have distinguishable filenames and use separate menu colours consistent with the requested Client and Client2 schemes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100