Re: Updated stream/parser todo

2006-07-06 Thread Han-Wen Nienhuys
Erik Sandberg schreef: On Tuesday 27 June 2006 13:08, Han-Wen Nienhuys wrote: Erik Sandberg schreef: The attached patch makes my proposed change to sequential-iterators, and uses this to clean up multi measure rests. The patch obsoletes the following: - glue-mm-rests - MultiMeasureRestMusicGrou

Re: Updated stream/parser todo

2006-06-28 Thread Nicolas Sceaux
Erik Sandberg <[EMAIL PROTECTED]> writes: > Nicolas: Does the music display method look OK? (also I think I spotted a > harmless typo; correct me if I'm wrong) The method does look OK. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lis

Re: Updated stream/parser todo

2006-06-27 Thread Erik Sandberg
On Tuesday 27 June 2006 13:08, Han-Wen Nienhuys wrote: > Erik Sandberg schreef: > > The attached patch makes my proposed change to sequential-iterators, and > > uses this to clean up multi measure rests. The patch obsoletes the > > following: - glue-mm-rests > > - MultiMeasureRestMusicGroup > > - S

Re: Updated stream/parser todo

2006-06-27 Thread Han-Wen Nienhuys
Erik Sandberg schreef: The attached patch makes my proposed change to sequential-iterators, and uses this to clean up multi measure rests. The patch obsoletes the following: - glue-mm-rests - MultiMeasureRestMusicGroup - Sequential_music_iterator I know mm rests can be further cleaned up by c

Re: Updated stream/parser todo

2006-06-26 Thread Erik Sandberg
On Monday 19 June 2006 16:02, Erik Sandberg wrote: > On 6/19/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > > Erik Sandberg schreef > > > BTW: May I change Sequential_iterator::get_music_list to return > > > something like scm_call_1 (get_music ()->get_property > > > ("child-list-callback"), get

Re: Updated stream/parser todo

2006-06-19 Thread Jan Nieuwenhuizen
Han-Wen Nienhuys writes: >> Not necessarily; the unclean workarounds are temporary and isolated, >> and will only last until we decide to drop backward compatibility. > > I don't see the point of temporary workarounds: either we solve a > problem completely or we don't. There's nothing as long-las

Re: Updated stream/parser todo

2006-06-19 Thread Han-Wen Nienhuys
Erik Sandberg schreef This doesn't sound like a very clean solution, which is troublesome given that the original (IIRC) motivation was to clean things up. Not necessarily; the unclean workarounds are temporary and isolated, and will only last until we decide to drop backward compatibility.

Re: Updated stream/parser todo

2006-06-19 Thread Erik Sandberg
On Friday 16 June 2006 14:46, Han-Wen Nienhuys wrote: > Erik Sandberg schreef: > > On 6/16/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > >> Erik Sandberg schreef: > >> > 3. Make translators listen to stream events, and make MusicEvent > >> > >> stream-events > >> > >> > contain properties direc

Re: Updated stream/parser todo

2006-06-16 Thread Erik Sandberg
On 6/16/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Erik Sandberg schreef: > 3. Make translators listen to stream events, and make MusicEvent stream-events > contain properties directly. Furthermore, represent all events as stream > events rather than music from the beginning. I think this

Re: Updated stream/parser todo

2006-06-16 Thread Han-Wen Nienhuys
Erik Sandberg schreef: 1. Interface for exporting/importing music streams: - refactor global-context-scheme: separate run-translator into three separate functions: 1 ly:make-global-context: initialise and create empty Global_context 2 ly:make-global-translator: create translators for an

Updated stream/parser todo

2006-06-14 Thread Erik Sandberg
Hi, There is a bunch of fairly independent next steps for me. I'd like to start with 3, because it's the biggest one, so I can work on 1+2 whenever 3 stalls. 1. Interface for exporting/importing music streams: - refactor global-context-scheme: separate run-translator into three separate functi