|
From: | Phil Holmes |
Subject: | [GLISS] - alternative viewpoint |
Date: | Fri, 14 Sep 2012 17:56:45 +0100 |
If you follow what is asked on -user, it's this stuff that causes confusion, not pre- or post-fix.
Now - I have no idea if this is possible or not, but when I put some of these complex overrides into my converter, the commands to the converter use a C-like syntax. For instance, I've written a feature that allows the converter to scale durations:
scaleDurationsOn(n,m)I personally think that providing more of these simple syntax features would make it much easier for the average user: we do have a few shortcuts of this type: for example:
autoBeamOff = \set autoBeaming = ##fmelismaEnd = #(context-spec-music (make-property-unset 'melismaBusy) 'Bottom)
Why not focus on making the slightly complex part of Lilypond much simpler (not the very complex, like customer scheme functions - if you can do that, you don't need help)? And getting rid of case-sensitivity in a lot of this? And providing error messages when an override has no effect because it was at the voice context and should have been at staff?
-- Phil Holmes
[Prev in Thread] | Current Thread | [Next in Thread] |