There are other options. Either way lets hold off on this for now.

I think a good time would be when we are about to go live and we have the site design figured out.

This change implies support for adding naturals in the visual score in case there is a lowered or raised note on the same degree in the same bar.

Represent each application state in the URL.

That way states can be bookmarked and shared. It also supports navigation through the browser history.

Let's use elm style elements.

I think the .travis.yml is a bit outdated. It could be updated according to latest versions/features/best practices.

E.g. scale+formula+settings per bar / 2..n bars ...

Suggestions:

• Skäalenmeister
• scales-meister
• Scales-O-Rama

• https://musical-artifacts.com/artifacts/3
• in the footer

The user should be able to enter arbitrary formulas in addition to the ones provided by the app.

E.g. when user clicks on formula button, they can enter something like "+2+2-1-1+3", or pick one from the shown list.

• Slider to change bpm

Time signature most of all

• Playback on mobile phones in a resource efficient way
• Maybe rely on Tone.js synth or something like this

Apply workaround

• special sound to mark the first beat of the bar
• different sound for all the beats but the first

Something like: "tick tock tock tock"

• also add Fuzzy tests

Vexflow seems to be quite complicated, especially when we want to render things dynamically.

We could try abcjs instead.

It looks like abcjs also covers the MIDI generation and playback functionality which would simplify things by orders of magnitudes.

See #7 for initial work on this. This checklist was extracted from Main.elm in the PR.

• use a link button instead of just a link
• add elm package: http://package.elm-lang.org/packages/newlandsvalley/elm-binary-base64/latest
• use the toMidi function from above to convert the 12 tone row to a byte array and convert the byte array to a string using encode from http://package.elm-lang.org/packages/newlandsvalley/elm-binary-base64/latest
• replace text "Download" with fontawesome download icon
• check correct midi specification
• convert tone sequence into valid midi format

• install
• run
• deploy
• etc

resolved by #72