lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: file structure (hierarchy)


From: Graham Percival
Subject: Re: file structure (hierarchy)
Date: Wed, 13 Feb 2008 06:57:12 -0800

I, however, *am* entirely opposed to that idea.  :)

LM 3.1.1 - 3.1.3 address the issue of overall file structure.
Best practices are introduced in LM 2.1.3 and LM 5.  We have a
whole (as-yet unworked) chapter devoted to "best practices"!
I certainly don't think we need to complicate every single example
in the manual just so that people don't need to read LM 3.1.3.

Of course, it may be that these sections aren't perfect; you
already found one problem, which Trevor will address.  I'd
forgotten about the \header issues, and I'm sure that Trevor never
knew about them.

Cheers,
- Graham


On Wed, 13 Feb 2008 11:20:54 +0100
Mats Bengtsson <address@hidden> wrote:

> We've had this discussion before. I'm not entire opposed to the idea
> of always
> specifying
> \score{
>   \new Staff {
>     \new Voice \relative c'{ c d e f }
>   }
> }
> in the examples in the manual. Making LilyPond too forgiving and
> helpful in terms of input syntax is sometimes a pedagogical problem,
> as soon as you get past the initial simple examples. On the other
> hand, keeping the initial threshold
> as low as possible for new users, is also a good goal.
> 
>    /Mats
> 
> Bertalan Fodor (LilyPondTool) wrote:
> > I think certain conventions could ease learning and using the
> > syntax, understanding snippets and so on. Do we have such
> > conventions defined? Because while it seems to be a good thing that
> > you can write { c d e f } and it will compile and generate score,
> > but if you want to create some polyphonic piano music you would
> > never use constructs like this. And with more complicated scores
> > users of LilyPond usually end up with completely different styles,
> > which makes learning LilyPond harder. If we had recommended
> > conventions, perhaps it helped people, for example "always use the
> > context when overriding Grob properties". That may not be true but
> > may be clearer.
> >
> > Bert
> >
> >
> 
> -- 
> =============================================
>       Mats Bengtsson
>       Signal Processing
>       Signals, Sensors and Systems
>       Royal Institute of Technology
>       SE-100 44  STOCKHOLM
>       Sweden
>       Phone: (+46) 8 790 8463                         
>         Fax:   (+46) 8 790 7260
>       Email: address@hidden
>       WWW: http://www.s3.kth.se/~mabe
> =============================================
> 
> 
> 
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user




reply via email to

[Prev in Thread] Current Thread [Next in Thread]