Re: [Denemo-devel] Import filter for CapXML

[Andreas Schneider]

Am 13.04.2015 um 10:12 schrieb Richard Shann:
> The main problem with basing your import on Denemo's XML import (ie the
> file src/core/importxml.c rather than src/export/importmusicxml.c) is
> the obscurities that you will see in src/core/importxml.c  starting at
> the main function importXML() and the associated parseMovement() just
> before - the creation of staffs, insertion of notes etc is all
> accompanied by calls to functions to set up things for the display
> appearance which are poorly understood.
> 
> What might be good is to parse CapXML and write Denemo's XML saving that
> to a temporary file and then load it. This would mean that all the
> obscure calls to staff_beams_and_stems_dirs () and a half-a-dozen others
> continue to be done by src/core/importxml.c and not repeated in your new
> importer. There is some obsolete fields in src/core/importxml.c which
> are no longer present in modern .denemo files, so these should be
> skipped - mostly I hope they are marked as "backward compatibility".

So do you think it would be better/easier to use the Scheme approach?

Andreas