[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Write a custom backend?
From: |
David Kastrup |
Subject: |
Re: Write a custom backend? |
Date: |
Tue, 13 Sep 2016 14:04:04 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Mathieu Demange <address@hidden> writes:
> Hello all,
>
> Could anybody help me to know if writing a custom output backend (in
> scheme, of course) for Lilypond is something doable? I mean without
> modifying any of Lilypond's internals.
>
> I believe the output backend principle is a good sign of extensibility
> but is it really the case? How to instruct Lilypond to use a custom
> one, then?
You'd have to make use of one of the existing translator groups (like
Engraver_group or Performer_group) which might me more accurately called
translator groupers: there is currently no way to define those in
Scheme.
Personally, I'd consider it a great project to convert _all_ of Midi
generation to Scheme.
--
David Kastrup
- Write a custom backend?, Mathieu Demange, 2016/09/13
- Re: Write a custom backend?,
David Kastrup <=
- Re: Write a custom backend?, H. S. Teoh, 2016/09/13
- Re: Write a custom backend?, Knut Petersen, 2016/09/14
- Re: Write a custom backend?, David Kastrup, 2016/09/14
- Re: Write a custom backend?, Knut Petersen, 2016/09/14
- Re: Write a custom backend?, David Kastrup, 2016/09/14
- Re: Write a custom backend?, Mathieu Demange, 2016/09/20
- Re: Write a custom backend?, Urs Liska, 2016/09/20
- Re: Write a custom backend?, Mathieu Demange, 2016/09/20
- Re: Write a custom backend?, Urs Liska, 2016/09/20