The development team should be present at the 2005 Linux Audio
Developers Meeting (april 2005) in Karlsruhe. This requires
writing a paper, which I plan to do myself. Nevertheless,
interested writers are welcome to contact me, should they wish
to attend as well. For example, it
Does it have to be about software? Otherwise, it might be interesting
to write something about public music archives like Mutopia, which is
a phenomenon that's much less spread than public software, but still
has many common denominators.
/Mats
Erik Sandberg wrote:
Hi all,
I am now taking a
Carl Sorensen [EMAIL PROTECTED] writes:
guile (define-module (*anonymous-ly-1*))
Since that thread, the first guile module name used in the lily file
has changed: (*anonymous-ly-0*) iso (*anonymous-ly-1*).
Nicolas
___
lilypond-devel mailing
Han-Wen Nienhuys [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] writes:
example, it would be interesting to have a case-study of advanced
LilyPond use.
I have some examples of advanced LilyPond use here.
Also enough material for a real case study?
(Actually, I was trying to provoke
In message [EMAIL PROTECTED], Graham
Percival [EMAIL PROTECTED] writes
On 5-Nov-04, at 4:49 AM, Han-Wen Nienhuys wrote:
WEBSITE
The current website is a lot better than we had; I'm glad it has some
interesting articles, and that it refreshes a lot (basically, for
every Lilypond release), but it
On 9-Nov-04, at 1:18 AM, Mats Bengtsson wrote:
Does it have to be about software? Otherwise, it might be interesting
to write something about public music archives like Mutopia, which is
a phenomenon that's much less spread than public software, but still
has many common denominators.
Actually,
On Tue, 2004-11-09 at 13:32, Nicolas Sceaux wrote:
Since that thread, the first guile module name used in the lily file
has changed: (*anonymous-ly-0*) iso (*anonymous-ly-1*).
Thanks! That fixed it.
Carl
___
lilypond-devel mailing list
[EMAIL
I'm trying to make a FretDiagram context and a Fret_diagram_engraver to
better implement fret diagrams.
Here's what I've done:
1. Copied ChordNames context in ly/engraver-init.ly
Modified as it seemed to make sense to me.
\context {
\type Engraver_group_engraver
\name FretDiagram
