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
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-
Hello, all --
Han-Wan wrote:
(stretching the analogy). I think it is better to just have a simple
portable bookcase as a demonstration.
Actually, as you probably know, reverse engineering is not easy (for
most people) -- it's the PLANS that are the most helpful, based on most
people's learning
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
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
[EMAIL PROTECTED] writes:
>
> Thanks for setting it up and thanks to Han-Wen for getting the links to
> the Wiki up so fast.
(Now let's hope that the wiki doesn't go down every weekend, like this
weekend)
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
__
> Nick Busigin <[EMAIL PROTECTED]> writes:
>
> > Question: Will the examples in the Wicki eventually end up on the
> >official "Tips & Tricks" page?
>
On Mon, 12 Jan 2004, Ferenc Wagner wrote:
> Yes, if somebody submits an appropriate patch to the
> maintainers. The Wiki should b
[EMAIL PROTECTED] writes:
> Nick Busigin <[EMAIL PROTECTED]> writes:
>
> > Question: Will the examples in the Wicki eventually end up on the
> >official "Tips & Tricks" page?
>
> Yes, if somebody submits an appropriate patch to the
> maintainers. The Wiki should be a temporary disc
Nick Busigin <[EMAIL PROTECTED]> writes:
> Question: Will the examples in the Wicki eventually end up on the
>official "Tips & Tricks" page?
Yes, if somebody submits an appropriate patch to the
maintainers. The Wiki should be a temporary discussion
and information gathering place.
e: Fri, 9 Jan 2004 18:29:47 -0800 (PST)
> From: Ray McKinney <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: SATB 2-staff template and request for suggestions
>
> Hello all,
>
> I'm a fairly new lilypond user, and most of my engraving will be choral music.
>
Ray McKinney <[EMAIL PROTECTED]> writes:
> The main point of this example, however, is to point out a
> way to right-justify the part names before the first
> staff. I know it took a lot of digging, reading, and
> trial-and-error before I found a way to do it. I've found
> several cases in the mai
Hello all,
I'm a fairly new lilypond user, and most of my engraving will be choral music.
I found the SATB example in the documentation helpful, but frequently choir
music is reduced to two staves. The main point of this example, however, is to
point out a way to right-justify the part names befor
20 matches
Mail list logo
