Re: file structure (hierarchy)

[Bertalan Fodor (LilyPondTool)]

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

--
LilyPondTool is the editor for LilyPond files.
See http://lilypondtool.organum.hu



_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user