GSoC 2018 - Beginner Mode and Tutorial Creation - Week 1
This is my weekly update on my Google Summer of Code project. There will be three parts of this blog post: what I did, what had issues, and what is next. Then, I will end it with a question that I need answered for part of the project.
What I did
New project scope
- MarcSabatella decided that my original project scope was too large and not all relevent. So, I have spent the past week revising and reducing the scope to better fit a summer of code. This can be found here. More information about the revised scope can be found in my first project description blog post.
- As part of the new scope, Marc wanted me to create an updated proposal. I study the source code, talked with Daniel Ray, and fully revised the original proposal. This can be found in the link above.
What had issues
- Defining the project
- The hardest part of this week was compiling multiple different opinions and picking out what was most important. There were multiple revisions done on the project and everyone had a different opinion.
What is next
- Workspace expansion
- My first actual code will involve expanding the existing workspace to include custom toolbars (saved onto the actual workspace), customizable menu items, and a select set of preferences (GUI only).
Question for the Week
On my proposal linked above (under "New project scope"), Marc commented that there may be more important things than action limiting. The main ones mentioned are On-Screen Help and a Tour of MuseScore. Briefly, a Tour of MuseScore would run the user through the basic features with pop up windows or something of the sort. So, my question is: Is action limiting more important or is something else better to spend my time on first? If it is something else, is it on-screen help, tour of musescore, or something else (it must go along with the general project)?
I’ll list a branch when I have one