Community Blog

Work Planned to be Done:

The work I planned to do for the third week of the coding period was to introduce the TreeView on the PaletteBox. This included adding classes to make the Tree Model.

Work Done:

Most of the time I worked on making the Tree Model from the data containing the names of the Palette which was placed on the file default.txt. Here I created the model using the text file and connected it to the treeView

My task this week has been to implement automatically changing key for transposing instruments, which in my mind is probably the most important part of the project that I have done so far. I spent a lot of time learning about how key signatures worked, especially with regards to transposing instruments, and key signatures that only applied to a single stave. After doing this, I attempted to implement automatically adding a key change object to each stave that was affected

This week was a bit of a long week, but it's finally over :)

So Far

Last week I was able to to clean up chord realization a bit. Previously, the algorithm just stacked thirds to create the notes. Now it's a bit better behaved and defined. There is a bass note (which may be the root if the chord is not a slash chord) placed in the octave below middle C and then the rest of the chord is

The third week's work still focuses on the fetching routine for plugins stored on musescore.org.

What I have done

1. Improvements on the scoring algorithm
   The scoring algorithm, briefly described in last week's blog, gives a score for each matched link found within the plugin detail page, to indicate how much likely it is to be the suitable download address.

   Before, only the filename was used to estimate scores. Now, multiple pieces of info are used via the following approach:

This blog post provides a brief report on the work I have done in the second week in the coding period of the Google Summer of Code program

Work Planned to be Done:

1. Construct a model using a QAbstractItemModel.
2. Make a Resource file to handle the data provided to make a treeView resembling a Palette.
3. Construct a Model using the .xml file containing all the Palette Items.

Work Done:

Construction of a TreeView with a model using the QAbstractItemModel.

I

After last week's work of automatically opening the instrument change dialog when an instrument change is added, my goal this week was to automatically change the instrument change text to the newly selected instrument.

After a bit of experimentation, this turned out to be a fairly simple thing to do, using the trackName() function on the instrument template, which gets the long name. There is some scope for future work for allowing the user to choose which name to use

Hi!

These days I have been focused on fetching plugins stored on musescore.org.

What I've done

1. I made some draft specifications on the format of upoaded plugins, including GitHub ones and musescore.org ones. You can see the detailed specifications on https://musescore.org/en/node/286338#comment-925465

   The main idea is that one GitHub repo must contain exactly one plugin, and place plugins of different versions on separate branches.

   And for musescore.org ones, we explicitly do not support the case where multiple qml files are uploaded

Made some good progress this week moving forward despite dead week work!

So Far

This week I have accomplished most (arguably all :)) of what I set out to do. I'm still in the progress of cleaning up the code into a more robust data structure to prepare for the next steps, but the data structure is integrated and running. I've also got a very simple system of realizing full chords and all of their notes. It's stacked triads over

Hi, sorry to be late. Now it's already the second/third day of week 2 in GSoC coding period, depending on your time zone.

What I've done

• Make the button style in plugins tab consistent with the extensions tab.

There're now always 2 buttons for each plugin. One is for install/update and the other is uninstall. Also, the buttons are now stretched to fill up the table widgets.

The fonts' anti-aliasing should be enabled if you are not debugging the application,

After the community bonding period, this week has been the first week of coding for the Google Summer of Code. The start of the week was spent setting up the git repository, and becoming more familiar with the codebase.

Part of what I had planned to do in the first week was to add the instrument change button to the inspector, rather than to the right click menu. This has actually been implemented by Isaac Weiss (https://github.com/musescore/MuseScore/pull/5010), so