On 2010-04-12, Helge Hafting wrote: > Bernardo Barros wrote: >> ... with this method there isn't much difference of >> this and importing the PDF already. It's not less work.
> It is slightly less; LyX will manage the creation of PDFs itself, you > will not need to update the PDF when changing the .ly file. > Of course, embedding lilypond code in LyX would be even less work. But I > don't know a quick way to program that. ... It should/could be done similar to "literate programming" and "R/Sweave" support. ... > What you want can be done though. Lilypond code could be stored in the > .lyx file, and LyX could write out a temporary .ly file and process it > with lilypond. There is already the lilybook program that does this separation/processing/replacement for Lilypond code in a tex file. Hence, LyX should export a tex file and then process it with lilybook before carrying on with latex ... > You may want to file an enhancement request for this at > http://www.lyx.org/trac/wiki/BugTrackerHome > so your idea is not forgotten. Also, this has been discussed on this (or the devel) list some time ago. AFAIK the framework for an implementation is now in place. Günter
