On Tue, 13 Jan 2004 22:31:09 +0100 (MET)
Alexander Deubelbeiss <[EMAIL PROTECTED]> wrote:
> On Tue, 13 Jan 2004 10:14:24 -0500 (EST), Nick Busigin wrote:
> > While we are on the topic of examples, my wife and I would be interested
> > in contributing a complete lead sheet example. However, we don'
On Mon, 12 Jan 2004 22:06:30 -0500
Kieren Richard MacMillan <[EMAIL PROTECTED]> wrote:
> However, for my own learning curve -- especially when I'm a newbie in
> some field -- I find it useful to see "real-world" examples, which
> almost by definition will include tens (if not hundreds) of
> tip
On Wed, 14 Jan 2004, David Raleigh Arnold wrote:
> Mutopia can be very helpful, but there are problems with the
> files there as examples:
>
> 4. Last, there is some questionable notation here and there. There
> is a great need for constructive criticism, and I don't feel that
> it would be appre
On Wednesday, January 14, 2004, at 07:14 AM, David Raleigh Arnold
wrote:
On Tuesday 13 January 2004 17:30, Kieren Richard MacMillan wrote:
Nick:
Kieren, what you are suggesting definitely makes sense. The more
examples the better, especially if they are written in a style and
with comments that
In message <[EMAIL PROTECTED]>
David Raleigh Arnold <[EMAIL PROTECTED]> wrote:
[...]
> Mutopia can be very helpful, but there are problems with the
> files there as examples:
>
> 1. It is not clear before download what version of lilypond was used to
> create a file. There is a very
On Wed, 14 Jan 2004, David Raleigh Arnold wrote:
> Mutopia can be very helpful, but there are problems with the
> files there as examples:
>
> 1. It is not clear before download what version of lilypond was used to
> create a file. There is a very nice footer at the bottom of
> Mutopia-2004/01/
On Wednesday 14 January 2004 14.14, David Raleigh Arnold wrote:
> On Tuesday 13 January 2004 17:30, Kieren Richard MacMillan wrote:
> > Nick:
> > > Kieren, what you are suggesting definitely makes sense. The more
> > > examples the better, especially if they are written in a style and
> > > with c
On Tuesday 13 January 2004 17:30, Kieren Richard MacMillan wrote:
> Nick:
> > Kieren, what you are suggesting definitely makes sense. The more
> > examples the better, especially if they are written in a style and
> > with comments that make it easy to follow what you are doing with
> > the lily c
On Tue, 13 Jan 2004 10:14:24 -0500 (EST), Nick Busigin wrote:
> While we are on the topic of examples, my wife and I would be interested
> in contributing a complete lead sheet example. However, we don't wish
> to place the composition in the public domain. I think that rules
> Mutopia out. Is
Nick:
Kieren, what you are suggesting definitely makes sense. The more
examples the better, especially if they are written in a style and with
comments that make it easy to follow what you are doing with the lily
code and possibly why.
Well said!
My purpose was merely to point out that a resourc
On Tue, 13 Jan 2004, Kieren Richard MacMillan wrote:
> What makes sense to me (and, perhaps, no one else?) is a dozen or more
> "standard" examples -- like the Satie and Schumann pieces, but widely
> ranging in "purposes", and intentionally developed as teaching/learning
> aids -- used as step-
step guides.
Jan wrote:
There are more problems with "intermediate examples": they cannot be
used for simple documentation or 'regression testing', where one
feature is tested, explained and indexed, they need to be actively
maintained, and by cramming too much complexity in examp
On Tue, 13 Jan 2004, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > almost by definition will include tens (if not hundreds) of
> > tips/tricks/techniques working together towards a well-defined,
> > "useful" goal. Being shown how a bolt fits into a nut is one thing;
> > seeing fourtee
[EMAIL PROTECTED] writes:
> almost by definition will include tens (if not hundreds) of
> tips/tricks/techniques working together towards a well-defined,
> "useful" goal. Being shown how a bolt fits into a nut is one thing;
> seeing fourteen bolt-and-nut combos combined with three pieces of
> d
n or 'regression testing', where one
feature is tested, explained and indexed, they need to be actively
maintained, and by cramming too much complexity in example files it's
easy to scare new users away.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The mu
Hey, y'all...
Han-Wen Nienhuys wrote:
For the tips & tricks, it is best if the each example is stripped to
its
bare essentials, and only demonstrates one and only one tip or trick.
I would agree with this *to a point*.
However, for my own learning curve -- especially when I'm a newbie in
some
16 matches
Mail list logo
