This is a work in progress, Cross-Platform Music Notation API written in Swift. It is written so that it can be used in most any operating system, such as iOS, macOS, Android, Windows, and Linux assuming that Swift is ported to these platforms. This library is being created with the goal of having 0 dependencies; not even Foundation.
If you are looking for the ability to display the music in an application, please see MusicNotationKit, which depends on this core library.
Please consult this Swift style guide for coding style guidelines used in this repo and be sure to adhere to them.
There is a Slack channel you can join if you want to see more into the development process at Music Notation Swift Slack.
This library is meant to provide an easy-to-use API for creating tablature or staff music to be displayed or played in an application. The library is not meant to deal with any UI or Audio, so that it may be used with any other UI or Audio frameworks.
There is also a plan to create an easy to use input file format to create the music instead of having to create the objects in code as it stands right now. Hopefully a file format can be developed that will be able to make it so simple that a musician who is not necessarily tech savy, would be able to create sheet music or tablature. There are also some open file formats that may be looked into, such as MusicXML (http://www.musicxml.com).
Currently unimplemented, but coming soon.
git checkout the repository somewhere that your project can find it. You can use git subtree or git sub modules method to keep the projects in sync, or use
modulo as a source only dependency manager, or yet still, simply keep them co-located and manage things manually.
To add a sub project (such as this) as a build dependency for your project, follow these steps:
Frameworksgroup to your project.
This library is under the MIT license. You can use it freely. We'd love to hear about if you use it, so let us know. Feel free to reach out to Steven Woolgar.
If you are interested in contributing, feel free to pick an issue and start to look into it. However, we suggest contacting us to get more info until we have created a full contributing guide. Contact Steven Woolgar for more details.