Re: Architecture for Fret Diagrams

2004-07-23 Thread Carl Sorensen
On Thu, 2004-07-22 at 16:24, Han-Wen Nienhuys wrote: > I would not base anything on the chord name itself (ie. the output > string). Systems for chord names are highly non-standard, so they're > not a good basis to interpret. I suppose that you would have to > devise some kind of lookup structure

Re: Architecture for Fret Diagrams

2004-07-23 Thread Carl Sorensen
On Fri, 2004-07-23 at 10:06, [EMAIL PROTECTED] wrote: > As I said before, I really do love the quality of Lilypond output. So I hope > you'll take this in the spirit it's intended: observations from a domain > expert > that may or may not be useful to you in the future. > Thanks for the input. I'

Architecture for Fret Diagrams

2004-07-22 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > I've been studying and thinking about architectures for Fret Diagrams in > lilypond. > > It seems to me that there should be a FretDiagrams context which would > process exactly the same music expression as the ChordNames context. > Then, a lead sheet with fret diagram

Architecture for Fret Diagrams

2004-07-19 Thread Carl Sorensen
I've been studying and thinking about architectures for Fret Diagrams in lilypond. It seems to me that there should be a FretDiagrams context which would process exactly the same music expression as the ChordNames context. Then, a lead sheet with fret diagrams could look like: \score { <<