GSoC/2018/StatusReports/AmanKumarGupta: Difference between revisions

From KDE Community Wiki
< GSoC‎ | 2018‎ | StatusReports
Line 119: Line 119:
* [https://cgit.kde.org/gcompris.git/log/?h=gsoc_aman_piano_activities Piano activities]
* [https://cgit.kde.org/gcompris.git/log/?h=gsoc_aman_piano_activities Piano activities]


==Important Links==
==Blog post links==


* [https://amankumargupta.wordpress.com/2018/06/04/gsoc-week-2-3/ GSoC 2018: Week 2 and 3]
* [https://amankumargupta.wordpress.com/2018/06/04/gsoc-week-2-3/ GSoC 2018: Week 2 and 3]

Revision as of 16:50, 11 June 2018

GCompris: Port all GTK+ piano activities to Qt and get one step closer to version 1.0

GCompris is an educational software suite comprising of numerous activities for children aged 2 to 10. Originally written in Gtk+ its development team started to rewrite it from scratch in Qt Quick. My aim is to port all the piano-based musical activities which are one of the most important activities that we are missing to have a complete 1.0.

Mentors: Divyam Madaan and Emmanuel Charruau

Project Goals

  • Finish the port of Piano composition activity and add more features.
  • Porting of GTK+ Play piano activity from scratch to QtQuick.
  • Re-design and implement Note names activity.
  • Porting of GTK+ Play rhythm activity from scratch to Qt.
  • Build GCCreationHandler, a tool which is to be used to import/export and manage user creation files of various formats and integrate it with configurable activities.

Work Report

Community Bonding Period

During the community bonding period, I've been in constant touch and communication with my mentors, discussing various aspects of implementing the activities. We had to change the plan of the activity Note names than the one I had planned in the proposal as we explored better ways and pedagogic interests which would be more helpful in remembering the notes. Also I extended a new branch from the HEAD of master and rebased the previous branch on top of it to continue my works during GSoC in it. Further I've been working with KDE since the past one year and have also participated in the Season of KDE this year and sucessfully my project, thus I'm well practiced with building the project, working with branches, docementations and code-base and it all went pretty good for me during the Community bonding period.

Coding Period - Phase one (May 14th to June 12th)


Piano Composition

Introduction:

This activity teaches the users how to compose melodies with piano by offering them certain components like notes, rests and many features like erase, replace, undo etc.

Implementation:

1. Improved melody loader window UI.

2. Made multiple staff view flickable and add more staffs when needed.

3. Reworked the code base according to IPN Notation.

4. Added contexts for translators.

5. Added rests.

6. Added replace and erase toggable features.

7. Added undo feature.

8. Separated Note data from the Staff view.

9. Added feature to display lyrics and other details of the music loaded.

10. Automated playing of piano when a melody is started.

11. Made note-type options toggable.

12. Added more octaves for treble and bass clefs.

13. Created new SVG images with ledger lines.

14. Did code cleanup and refactorizations.

Status:

The activity is currently under testing and review.

Screenshots:

Music Loader window

Melody composed with piano

Lyrics for the music loaded


Play piano

Introduction:

This activity aims to let the user understand how the piano keyboard can play rythm as written on the musical staff by replicating the ones that are presented.

Implementation:

1. Added resources from the Gtk+ version.

2. Laid down UI of the activity.

3. Added levels dataset.

4. Implemented working logic of the activity.

5. Added configuration for two modes: colored notes and colorless notes.

5. Code refactorization.

Status:

The activity is currently under review.

Screenshots:

Levels with colored notes to replicate the rhythm

Levels with colorless notes to replicate the rhythm

Configuration window for the two modes

Branch where I'm working

Since all the activities will be built upon a common API and need to be sharing lots of code, I'll be carrying all my works in the branch:

Blog post links

Contact

Email: [email protected]

IRC: gupta2140[m]

Github: gupta2140