Hi Stefano,
>> 4. Things would be way easier if the EE (and/or Frescobaldi) had a method to
>> highlight (colour-ing the grobs?) all mods, and a linking method to
>> navigate to the correct spot in the edition file. There was an example of
>> this [colouring part] some time ago, but I don't
>
> 4. Things would be way easier if the EE (and/or Frescobaldi) had a method
> to highlight (colour-ing the grobs?) all mods, and a linking method to
> navigate to the correct spot in the edition file. There was an example of
> this [colouring part] some time ago, but I don't know if it was
Hi Jan-Peter,
On Feb 20, 2018, at 4:46 AM, Jan-Peter Voigt wrote:
> At least I used it a lot in a score containing lyrics to balance the
> syllables in order to get the rhythmic picture of the score intact.
A staggeringly large percentage of my \editionMods are Lyric-nudges.
Hi Urs,
>> 1. Use of \editionModList and other convenience "compressors" can,
>> in many cases, make for maintenance difficulties.
> interesting point.
Yes… I didn't really think about it until I was well into using it heavily.
OT: That inspired me to write this "compressed" score of "Mary Had
Am 20. Februar 2018 18:42:03 MEZ schrieb Kieren MacMillan
:
>Hi Stefano,
>
>> I am undecided on what the best interface for it would be though,
>since as Urs already mentioned there are trade-offs with each
>possibility. I too think that a discussion should be had
Hi Stefano,
> I am undecided on what the best interface for it would be though, since as
> Urs already mentioned there are trade-offs with each possibility. I too think
> that a discussion should be had about that, to see what use-cases and needs
> arise. How do you usually do that here? Do
I completely missed development1.ly, that is great! The way the proc is
managed is particularly useful. It seemed to me that all the ingredients
for a convenience function are already there.
I am undecided on what the best interface for it would be though, since as
Urs already mentioned there are
Thank you all for your responses to my original post, and for the
ensuing discussion which I am following with great interest. I shall
not reply to each response individually, mainly because I have little
to offer that would be constructive: I made my original post because it
was my view as a
Hello Stefano,
this is a great idea! Setting global context variables can reduce the
needed code significantly.
In
https://github.com/openlilylib/edition-engraver/blob/master/usage-examples/development-1.ly
I use global variables to create "dynamic" editionModLists.
The files development*.ly
I've been wanting to expand my earlier tutorial with a section dealing with
\editionModList since I think the convenience of it can be useful to many
users. However, it is not a solution for every situation. Particularly, it
is not useful when you need to insert objects as part of your edition if
Hi Jan-Peter,
> to address multiple contexts at once you can use regular expressions and
> wildcards like in
> https://github.com/openlilylib/edition-engraver/blob/master/usage-examples/development-3.ly
YAY! I didn't know this was in there. (I'm sure I would have, if I had gotten
my head
Hi David,
Urs already answered. I understand your concerns about the input and I
am always open for ideas to ease the input for the edition-engraver.
Like Urs already mentioned your proposal will be difficult to implement
because it doesn't use the standard parser schemes. But it sheds light
Hi David,
19. Februar 2018 12:00, "David Sumbler" schrieb:
> As a newcomer to using Edition Engraver, and looking at the example
> files etc., I wondered why they were written with so much repetition.
> "Perhaps it is just to keep things easy for newcomers like me to
>
As a newcomer to using Edition Engraver, and looking at the example
files etc., I wondered why they were written with so much repetition.
"Perhaps it is just to keep things easy for newcomers like me to
understand," I thought.
So I experimented with reformatting using braces as Lilypond does,
14 matches
Mail list logo