[Top][All Lists]

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

Re: file structure (hierarchy)

From: Mats Bengtsson
Subject: Re: file structure (hierarchy)
Date: Wed, 13 Feb 2008 11:20:54 +0100
User-agent: Thunderbird (X11/20070716)

We've had this discussion before. I'm not entire opposed to the idea of always
 \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.


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.


        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden

reply via email to

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