Han-Wen Nienhuys writes:
> I would like to use the lilypond parser for my own application for
> some sort of composition tool. How complicated would it be to strip
> out that part of lilypond into some sort of library that would parse
> mudela text and hand back a collection of objects that represent
> music?
>
> Not very difficult, but it depends on what you want to do exactly.
> You might have to import a lot more than only the parser, just to make
> machinery such as identifiers work. It might be easier to just paste
> the relevant parts of the parser into a separate .y file.
>
I was thinking that I might use the exact same objects as lilypond.
Keep intact the notions of spanner, request, and all that. Everything
that has to do with how the music sounds would stay in. Basically, I
want to render music into a Python based compositional environment
instead of to paper (or a MIDI file) using Mudela. The advantages are
that Mudela would be a common link between my tool and Lilypond so I
would only need to know one language (plus I couldn't design a better
one, anyway), and it would be easy to dump my compositions back out in
a form suitable for notating with Lilypond. (In addition, so much of
the work is already done. 8-) )
John
--
John Galbraith email: [EMAIL PROTECTED]
University of Arizona, home phone: (520) 327-6074
Los Alamos National Laboratory work phone: (520) 626-6277
