You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2023. It is now read-only.
The GitHub demo page looks a little bit out of date -- I think it would be nice to add some examples showing the current capabilities of MEItoVexFlow. What do you guys think?
I'm asking myself if the options parameter of render_notation (src/Interface.js), which passes most of its parts to src/Converter.js, should be described in readme.md. That should depend on whether we consider it as a part of the official API or not -- generally, I would tend to add it, but I think we should discuss its design before.
The text was updated successfully, but these errors were encountered:
👍 I wish I had the time! :)
I think the readme should give a basic example of how to set up a working instance of MEItoVexFlow; all the parameters of render_notation can be explained elsewhere.
I fully agree - forgot about the js documentation in the meantime; providing it there would be the best place (I keep the issue open for the update of the github user page)
The GitHub demo page looks a little bit out of date -- I think it would be nice to add some examples showing the current capabilities of MEItoVexFlow. What do you guys think?
I'm asking myself if the options parameter of
render_notation
(src/Interface.js
), which passes most of its parts tosrc/Converter.js
, should be described inreadme.md
. That should depend on whether we consider it as a part of the official API or not -- generally, I would tend to add it, but I think we should discuss its design before.The text was updated successfully, but these errors were encountered: