I want to add them as a "tab" to our web site - so we can view and/or play scores at any point in the process. (For example, transpose a score, - look at it in the view/play tab - then add bass to in and look at it again)
If you can put the basic functionality of https://zan.dzb.fit/ into our project, I will try to integrate it into the current musicxml_process.htm page.
That I have in mind, is that you create a new .htm page (musicxml_view.htm) which views and plays a score (just like you do on the dzb site) We can keep musicxml_view.htm around for testing, etc. even after we integrate the view/play logic into our own page.
And that you create a single library javascript file, (if possible), called ABMXML_Lib_View.js in the music_common sub-folder which will have everything people need to add this functionality to their own GitHUB projects, and which I will load for use in the musicxml_process.htm.
We can have a second .js and .css file called musicxml_view.js and musicxml_view.css for things which we need in out .htm, but people would not necessarily need if they wanted to use out libraries in their own application.
That you put external libraries, which we do not need to modify) such as opensheetmusicdisplay.min.js in the libraries sub-folder.
And then I will try to make musicxml_process.htm load things properly and work, so I can see what I need to do to add the same functionality to musicxml_process.htm
Does that make any sense, and/or do you have any better suggestions?
I am ready to add the functionality to view and play a score to our website. If you agree, then we can start doing this.
The things you have at https://zan.dzb.fit/. look very good.
I want to add them as a "tab" to our web site - so we can view and/or play scores at any point in the process. (For example, transpose a score, - look at it in the view/play tab - then add bass to in and look at it again)
If you can put the basic functionality of https://zan.dzb.fit/ into our project, I will try to integrate it into the current musicxml_process.htm page.
That I have in mind, is that you create a new .htm page (musicxml_view.htm) which views and plays a score (just like you do on the dzb site) We can keep musicxml_view.htm around for testing, etc. even after we integrate the view/play logic into our own page.
And that you create a single library javascript file, (if possible), called ABMXML_Lib_View.js in the music_common sub-folder which will have everything people need to add this functionality to their own GitHUB projects, and which I will load for use in the musicxml_process.htm.
We can have a second .js and .css file called musicxml_view.js and musicxml_view.css for things which we need in out .htm, but people would not necessarily need if they wanted to use out libraries in their own application.
That you put external libraries, which we do not need to modify) such as opensheetmusicdisplay.min.js in the libraries sub-folder.
And then I will try to make musicxml_process.htm load things properly and work, so I can see what I need to do to add the same functionality to musicxml_process.htm
Does that make any sense, and/or do you have any better suggestions?