GSoC 2016 | Timeline dockable dialog

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

GSoC 2016 | Timeline dockable dialog

Homletmoo
Hi developers,

My name is Sam, and I’m a first year undergraduate at the
University of Cambridge, currently reading the Computer Science
tripos. I’m interested in applying for a Google Summer of Code
project this year.

I play piano and guitar, and enjoy digital music production. In
the past, I have used Musescore for the purposes of transcribing
music. In my experience, the usability of Musescore (ignoring the
initial learning curve) is somewhat hindered by slightly awkward
navigation, particularly for larger scores. For instance, the
position of the playback head is not always clear.

With this in mind, I was drawn to the suggestion of a timeline
dialog, which provides a chronological overview of the score, and
a means for navigation. One useful addition could be a persistent
playback head displayed on the timeline, which may be dragged
around by the user; currently the playhead on the score disappears
when not in playback.

I believe creating the timeline panel would be completely within
my reach, having previous experience with Qt (albeit using Python
bindings), and also a good knowledge of C++.

I plan on submitting an official proposal later this week, but
have a couple of questions beforehand:
    - Will I need to submit a code sample with my application?
      If so, what size, language etc.?
    - Would the fact that I have not contributed to Musescore in
      the past massively damage my application? I have worked on
      several projects in the past - both solo and as a team - but
      have never been involved in an established open source project.

Thanks and kind regards,
Sam Hubbard
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GSoC 2016 | Timeline dockable dialog

lasconic
Administrator
Hi Sam,

Also note that the deadline for application submission is March 25th. https://developers.google.com/open-source/gsoc/timeline

No code sample is needed. It's of course better if you can demonstrate that you can compile MuseScore and if you submitted a bug fix as a pull request. It's not required to be a long time contributor to MuseScore or any open source project. If you have a github account, please mention it in your application.

As you may know, Timeline is one of the ideas from our list https://musescore.org/en/developers-handbook/google-summer-code/ideas-2016#timeline didn't include the playback cursor but sure, why not. Note that something similar already exists in the View > Play Panel but working on a "unrolled" score (meaning repeats are unrolled and cursor never goes back).

We could also discuss about a persistent playback head in the score view. If you want, you can start a discussion on the feature request forum https://musescore.org/en/forum/7

Best,
lasconic

2016-03-22 6:02 GMT+04:00 Homletmoo <[hidden email]>:
Hi developers,

My name is Sam, and I’m a first year undergraduate at the
University of Cambridge, currently reading the Computer Science
tripos. I’m interested in applying for a Google Summer of Code
project this year.

I play piano and guitar, and enjoy digital music production. In
the past, I have used Musescore for the purposes of transcribing
music. In my experience, the usability of Musescore (ignoring the
initial learning curve) is somewhat hindered by slightly awkward
navigation, particularly for larger scores. For instance, the
position of the playback head is not always clear.

With this in mind, I was drawn to the suggestion of a timeline
dialog, which provides a chronological overview of the score, and
a means for navigation. One useful addition could be a persistent
playback head displayed on the timeline, which may be dragged
around by the user; currently the playhead on the score disappears
when not in playback.

I believe creating the timeline panel would be completely within
my reach, having previous experience with Qt (albeit using Python
bindings), and also a good knowledge of C++.

I plan on submitting an official proposal later this week, but
have a couple of questions beforehand:
    - Will I need to submit a code sample with my application?
      If so, what size, language etc.?
    - Would the fact that I have not contributed to Musescore in
      the past massively damage my application? I have worked on
      several projects in the past - both solo and as a team - but
      have never been involved in an established open source project.

Thanks and kind regards,
Sam Hubbard



--
View this message in context: http://dev-list.musescore.org/GSoC-2016-Timeline-dockable-dialog-tp7579729.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Loading...