Note: This repo currently contains adjustments to MEItoVexFlow to support better implementation of features of the MEI Snippet Viewer component. For the main branch of MEItoVexFlow, see http://tei-music-sig.github.io/MEItoVexFlow/
To build MEItoVexFlow, you'll need Node.js and npm. In the main directory run (skip the first step if you have bower and grunt already installed globally):
$ npm install -g bower grunt-cli $ npm install $ bower install
...and you're set! Now, to build run:
The library provides the function
render_notation which takes up to six
xmlDoc(XMLDocument) should be a markup fragment containing the MEI
target(Element) should be an HTML or element onto which the notation will be drawn
width(Number) should be the width of the canvas in pixels. Defaults to 800 (optional)
height(Number) should be the height of the canvas in pixels. Defaults to 350 (optional)
backend(Vex.Flow.Renderer.Backends.CANVAS|Vex.Flow.Renderer.Backends.RAPHAEL) specifies the VexFlow backend to use. Defaults to Vex.Flow.Renderer.Backends.CANVAS (optional)
options(Object) may contain additional conversion and rendering options; see the comments on the default options in
src/Converter.jsfor details (optional)
For sample function calls see the test runs in the 'tests' directory!
As part of the MEI2VexFlow project, MeiLib.js has been created to offer a set of VexFlow-independent methods, such as calculating timestamp value for a given musical event, or parsing information related to the Critical Apparatus MEI module.
For more information about the functions in MeiLib.js see the documentation comments within the source file meilib.js
- Any browser in which this code is used must have the VexFlow and jQuery libraries loaded.
- MEI2VexFlow uses MeiLib.js to convert timestamp values into xml:id values, therefore it cannot run without it, on the other hand,
- MeiLib.js can work independently from MEI2VexFlow. To use MeiLib.js on its own, simply download or reference the meilib.js file!
Only a small subset of MEI has so far been implemented. Many conventional aspects of common practice notation have been ignored (such as repeat accidentals). It's also important to remember that VexFlow is a moving target, it's in constant development and so this code could break at any time.
If you'd like to contribute to MEItoVexFlow, please do! This project is young and there is a lot to fix, so we don't have real style guidelines for now. However, before sending a pull request, make sure that the tests are still working.
Copyright © 2012, 2013 Richard Lewis, Raffaele Viglianti, Zoltan Komives, University of Maryland
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.