Summer of Code/2018/Music Blocks Widget Improvements: Difference between revisions
part2.5 Tag: visualeditor |
part2.6 Tag: visualeditor |
||
| Line 178: | Line 178: | ||
<nowiki>https://github.com/a-ritwik</nowiki> | <nowiki>https://github.com/a-ritwik</nowiki> | ||
=== '''You and the community''' === | |||
'''If your project is successfully completed, what will its impact be on the Sugar Labs''' | |||
'''community?''' | |||
My Answer - My project has 3 parts, I have explained their impact one by one1- Fixing existing bugs of different widgets in Music Blocks - There are currently several | |||
widgets in Music Blocks, and fixing existing bugs from them will enhance user experience, | |||
remove improper system behavior, and make Music Blocks more robust. | |||
2- Pitch tracker – After its completion, we can give input from microphone and use pitch | |||
tracking to generate Music Blocks code. So after this we do not have to manually code for | |||
each and every song, It could be done with good enough accuracy by the pitch tracker. As | |||
Devin Ulibarri has suggested It could be a GCI task to choose a song, sing it, and then submit | |||
both recording and Music Blocks code. | |||
3- Integrating software keyboard with Music Blocks- This would be implemented as a widget | |||
which on key press will give corresponding output as chunk. Currently the keyboard works | |||
fine but it looks very much different than the theme of Music Blocks. The project will create | |||
unity in design of keyboard with Music Blocks. | |||