QuantStack / QuantStack/jupyter-bluetooth-manager
Centralized list of issues to be addressed
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
- 1- Propose alternative designs for the ManualControl component and remove the descriptive text
PR: https://github.com/QuantStack/bluetooth-manager/pull/8 - 2- Improve the UI organization and responsiveness
PR: https://github.com/QuantStack/bluetooth-manager/pull/12 - 3- Add a menu to the connection status widget (combine the round status component, the connect and disconnect buttons into a single button)
PR: https://github.com/QuantStack/bluetooth-manager/pull/13 - 4- Improve command and button labels
PR: https://github.com/QuantStack/bluetooth-manager/pull/11, https://github.com/QuantStack/bluetooth-manager/pull/36 - 5- Prevent the external motor to be run outside of valid range of angles for Vernie's head
PR: https://github.com/QuantStack/bluetooth-manager/pull/10 - 6- Enable in ipymovehub widget the user to select an already connected Move Hub
PR: https://github.com/QuantStack/bluetooth-manager/pull/42 - 7- Behavior on browsers where Web Bluetooth is not supported
Issue: https://github.com/QuantStack/bluetooth-manager/issues/9
PR: https://github.com/QuantStack/bluetooth-manager/pull/30 - 8- Propose additionnal controls/demo in the user interface or examples like the hexagonal displacement or try all led colors in a loop like in the example notebook of the widget
- 9- Improve the design of turn right and turn left icons
PR: https://github.com/QuantStack/bluetooth-manager/pull/14 - 10 - Clarify the pairing process steps and possible failures and catch errors properly
Issue: https://github.com/QuantStack/bluetooth-manager/issues/40
PR: https://github.com/QuantStack/bluetooth-manager/pull/32 - 11- Set the same border for the headers and the other rows of the tables
PR: https://github.com/QuantStack/bluetooth-manager/pull/16 - 12- Replace the contextMenu attached to the RunningItem corresponding to the connected Device by a Menu
PR: https://github.com/QuantStack/bluetooth-manager/pull/43 - 13- Propose additionnal control buttons like half turn left and right if necessary or alternatively propose different behavior on click and press (click: quarter turn, press: turn until)
PR: https://github.com/QuantStack/bluetooth-manager/pull/44 - 14- Propose a try jupyterlite link
PRs: https://github.com/QuantStack/bluetooth-manager/pull/18, https://github.com/QuantStack/bluetooth-manager/pull/19, https://github.com/QuantStack/bluetooth-manager/pull/33, https://github.com/QuantStack/bluetooth-manager/pull/37https://github.com/QuantStack/bluetooth-manager/pull/34 - 15- Get the primary MAC address of the Move Hub and display it in the control panel.
PR: https://github.com/QuantStack/bluetooth-manager/pull/31 - 16- Add possibility to have a second motor connected to port C in the control panel.
PR: https://github.com/QuantStack/bluetooth-manager/pull/41 - 17 - Fix images to work with dark theme too (MoveHub, Vernie and Frankie images with transparent backgrounds, the battery gauge with white border, empty buttons with the same color as the color selector and the table cells.)
https://github.com/QuantStack/bluetooth-manager/pull/39
(Issues 1 to 5 are reported from comments of Issue https://github.com/QuantStack/bluetooth-manager/issues/4 from @GabrielaVives and @SylvainCorlay )
CC: @SylvainCorlay @afshin @GabrielaVives
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files or tests and mainly tracks completed work through pull requests. Review the remaining unchecked items, choose one narrowly defined UI or example task, and treat a focused change with its own validation and pull request as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100