As we're currently not really having a proper channel for making product level announcements like breaking changes or feature development that is ongoing I'm starting this issue where I'll try to keep you up to date about the things ongoing in alphaTab.

I'm not really a fan of social media portals as you might have realized on the FB and Twitter accounts of alphaTab 😅

I will leave the issu

Should be pretty easy, there's a Vexflow demo with about 20 lines total.
0xfe/vexflow#674
http://jsfiddle.net/9cd3s0v2/4/

This should be an OSMDOption that accepts a background color and stroke color.

bracketSpan@func documentation:

https://music-encoding.org/guidelines/v4/elements/bracketspan.html

func(required)Describes the function of the bracketed event sequence. Allowed values are: "coloration" (Represents coloration in the mensural notation source material.), "cross-rhythm" (Marks a sequence which does not match the current meter.), "ligature" (Represents a ligature in the mensu

Somewhere, probably at the top-level, an Examples directory could be created.
In there a sub directory could contain a small main function along with a CMakeLists.txt file. In that CMakeLists.txt file we should relay on this installation of mx and use find_package( mx ). During continuous integration runs, we should add a step where we make install then cd to the example and build it. If mx i

Now that we are disabling .trimValueWhitespaces from our decoder, it may make sense to create an XMLDecoder subclass MusicXMLDecoder.

This way we can use MusicXMLDecoder when testing atomic units, so we know we are working with the same thing when decoding a whole MusicXML object.

This will also allow us to wipe XMLCoder from testing, which has seemed slightly out of place.

• API consumers should only need to copy pasta the code in readme examples to get started?
• link galina's github via the npm page
• package fille need not show dev dependencies
• readme should include links to example scores
• make the purpose of toscanini and Iterator more distinct...

I have many years of experience in software developmen (C++, Python, QML and more).
In projects I was involved in using of tabs was either always discouraged, not allowed, automatically converted to spaced with git/svn or (many years ago) used in consence after issues using both.

There are advantages using tabs over spaces, mainly that everyone can set his own preferred tab size. However in my

Add a check box to turn show fingering on and off, default is on to the web interface at http://musicxml2braille.appspot.com