bug-lilypond
[Top][All Lists]
Advanced

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

Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage


From: lilypond
Subject: Re: Issue 1058 in lilypond: Frequent Errors should be moved from Usage to Learning
Date: Wed, 14 Apr 2010 16:45:01 +0000

Updates:
        Labels: -Priority-Medium Priority-Postponed

Comment #4 on issue 1058 by Carl.D.Sorensen: Frequent Errors should be moved from Usage to Learning
http://code.google.com/p/lilypond/issues/detail?id=1058

Ok -- I'll mark it postponed, and we'll see what happens after 2.14.

But I think that there needs to be some serious rewriting of the Usage manual Chapter 1 -- it's a very eclectic mix of what I would consider to be basic usage and what' I'd consider to be advanced usage.

When I look at the Manuals page on the new webiste, I see the following, in order:

Introduction:
  Text Input
  Learning Manual
  Glossary (Optional)
  Essay (Optional)

Regular Use:
  Notation
  Usage
  Snippets



So Usage is the 6th manual mentioned, or 4th if we exclude the optional manuals.

Suppose I'm a new user, working my way through the Learning Manual. And I make a mistake in durations, leading to a staff that runs off the page. How do I find the source of that error? Look through all gazillion pages of Notation? Then browse Usage? What about the link to Usage indicates that there might be a
"Common Errors" page in it?

I know you don't want a FAQ, because a FAQ represents a weakness that ought to be fixed in the documentation. And I agree with that. But I don't think that Usage is the best place for Common Errors. Actually, I suspect the best place for Common Errors is a link all by itself in the Introduction box.

But I still think that Learning is a better place than Usage...

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings




reply via email to

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