-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compiling to json or svg #432
Comments
@bbloomf what do you think? |
Even without the ability to compile gabc into json, it might be nice to have an alternative to jgabc but shares its codebase with gregorio, just so that the graphical output of the two tools could be expected to be more similar to each other. Would there really be a use case for compiling gabc into json though? It seems to me like it would probably only be a bit faster to parse json data than the standard .gabc file, but maybe having json files would allow for a more streamlined svg library that wouldn't be able to parse gabc but could handle the json version? However, I'm not sure that there's a real need for such streamlining these days. Anyway, it's an interesting idea. |
The idea was to have gregorio output something readable by js directly, then js would do the treatment, but you're right, outputing svg directly is a more direct (though less generic) solution |
See https://github.com/frmatthew/exsurge/ for an open-source gabc rendering js library, looking very good! |
An idea for the distant future: having code able to compile gabc to json, with information similar to those of the gtex output. Compiling it with Emscripten into asm.js would make a very strong replacement for jgabc...
The text was updated successfully, but these errors were encountered: