[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: First release of ly/

From: Marc Hohl
Subject: Re: First release of ly/
Date: Tue, 07 Jul 2009 20:20:20 +0200
User-agent: Thunderbird (X11/20090608)

I don't particularly mind breaking existing scores (as long as there is
a convert-ly rule to at least warn about the problem), but I don't think
the situation in the patch is particularly friendly. We've a long
tradition of choosing sensible behaviour over backwards compatibility
and I see no reason to change it now.

I am not sure whether I understand your comment correctly.
What should I change to make the patch more "friendly"?


I think that Joe means go ahead and break old scores --
Carl, thanks for clarification - I misunderstood Joe's message totally, as I can see now.
do the best thing
for going forward, so make TabNumbersOnly the default behavior (like you
wanted to), and have TabFullNotation be the override.  That is, ignore my
initial suggestion to keep TabFullNotation as the default behavior.

Ok. How should I put these things together?

As far as I can see, I should

1) put all the functions in a file scm/tablature.scm
  (I have to add this file in ly/, right?)

2) modify ly/ so that tablature without stems and stuff will be
  the default situation (where do I put the \TabFullNotation command?
  Is scm/tablature.scm the right place?)

3) move the existing predefined tunings from scm/output-lib.scm
  into tablature.scm, where I can add my new tunings as well;

4) include the function add-new-clef to scm/parser-clef.scm

5) modify ly/ and scm/music-functions.scm to include TabNoteHeads in the 'graceSettings list (a minor correction: fret numbers for grace notes
  should be set in smaller size)

6) put everything together in a patch ;-)

Any changes/corrections/improvements are appreciated!


I believe that will make things much more simple in the code if you do that.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]