Re: [PATCHES] Re: move .ly code out of .py

2009-02-20 Thread Han-Wen Nienhuys
I'm going away for carnival, but reviewed 2 patches for you. On Fri, Feb 20, 2009 at 7:36 AM, Reinhold Kainhofer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Apparently, my message got lost somewhere in the mail flood of lily-devel, so > I'm reposting my request for review of se

Re: [PATCHES] Re: move .ly code out of .py

2009-02-20 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Apparently, my message got lost somewhere in the mail flood of lily-devel, so I'm reposting my request for review of several patches: Any objections to applying these patches (those with a convert-ly rule of course only after 2.13 has been opened)? h

Re: [PATCHES] Re: move .ly code out of .py

2009-01-30 Thread Werner LEMBERG
> Patch to add the glyph to the feta font and define a corresponding > \snappizzicato articulation: http://codereview.appspot.com/12862 > > Werner, can you please take a look at the metafont code and check if > I did it the right way? Everything looks fine. Werner ___

[PATCHES] Re: move .ly code out of .py

2009-01-30 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Donnerstag, 18. Dezember 2008 15:45:28 Han-Wen Nienhuys wrote: > Can you put your timesig code into a .scm (or .ly) file ? We should > try to minimize nested code (ie code in language A inside code of > language B). Okay, finally here are some pat

Re: move .ly code out of .py

2008-12-28 Thread Han-Wen Nienhuys
On Sun, Dec 28, 2008 at 1:43 PM, Reinhold Kainhofer wrote: > Actually, those definitions are not only meant for musicxml2ly. They do not > depend on anything MusicXML-specific, but rather implement features that are > available in MusicXML, but not yet in LilyPond. They are candidates for future

Re: move .ly code out of .py

2008-12-28 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Donnerstag, 18. Dezember 2008 19:37:19 schrieb Han-Wen Nienhuys: > On Thu, Dec 18, 2008 at 1:14 PM, Reinhold Kainhofer > wrote: > > Am Donnerstag, 18. Dezember 2008 schrieb Han-Wen Nienhuys: > >> Can you put your timesig code into a .scm (or .ly) f

Re: move .ly code out of .py

2008-12-18 Thread Han-Wen Nienhuys
On Thu, Dec 18, 2008 at 1:14 PM, Reinhold Kainhofer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am Donnerstag, 18. Dezember 2008 schrieb Han-Wen Nienhuys: >> Can you put your timesig code into a .scm (or .ly) file ? > > yes and no (i.e. "yes" it should be added to lilypond directl

Re: move .ly code out of .py

2008-12-18 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Donnerstag, 18. Dezember 2008 schrieb Han-Wen Nienhuys: > Can you put your timesig code into a .scm (or .ly) file ? yes and no (i.e. "yes" it should be added to lilypond directly, but "no" not in its current form). Currently it's unfinished (aut

move .ly code out of .py

2008-12-18 Thread Han-Wen Nienhuys
Hi Reinhold, Can you put your timesig code into a .scm (or .ly) file ? We should try to minimize nested code (ie code in language A inside code of language B). -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel