Michael Rasmussen wrote:
Graham Percival wrote:
I've posted initial instructions for GDP helpers here:
http://opihi.cs.uvic.ca/~gperciva/helper.txt
I'll take pitches for $100, er first week.
Graham, for the git-able among us what is the path to the git repository?
(let's keep this on the ma
Erik Sandberg wrote:
But in any case: Engravers (which produce a sheet-music-friendly grob graph)
and Performers (which produce some midi-friendly data structure), are both
subclasses of Translators. If you are going to produce Braille output (which
is my guess for some unknown reason), you cou
2007/9/22, Trevor Bača <[EMAIL PROTECTED]>:
> On 9/21/07, Graham Percival <[EMAIL PROTECTED]> wrote:
> > Should we keep @refcommands independent from @commonprop ? For example,
> > look at Tuplets. Do you like it as it is, or should we move
> >
> > \tupletUp \tupletDown etc
> >
> > inside the "Co
On 9/21/07, Graham Percival <[EMAIL PROTECTED]> wrote:
> Should we keep @refcommands independent from @commonprop ? For example,
> look at Tuplets. Do you like it as it is, or should we move
>
> \tupletUp \tupletDown etc
>
> inside the "Commonly tweaked properties" ?
I vote for combine.
--
On Friday 21 September 2007, Ralph Little wrote:
> Hi,
> The code behind MIDI output and Performance seem to be pretty much
> tightly tied together.
>
> Was it ever intended that Performance be used for other output types?
> The Performance class contains specific MIDI references.
>
> I was under t
