[Top][All Lists]

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

Re: Examples (for the web site and complete scores) status

From: Jan Nieuwenhuizen
Subject: Re: Examples (for the web site and complete scores) status
Date: Mon, 12 Oct 2009 12:43:12 +0200

Op donderdag 06-08-2009 om 00:08 uur [tijdzone -0700], schreef Graham

> IMO, there are two kinds of examples here.
> 1)  advertizing examples: "we can do tabs, complex rhythms, lots
> of accidentals, gregorian chant, etc etc".  We expect people to
> glance at the image and then move on.
> 2)  educational examples: part of the documentation.  We expect
> people to read the source if they're interested.

You missed

  3) benchmarking/full feature examples/developer's/user's smoke tests


I'm a bit unhappy with the commit messages

    Remove mutopia
    Remove examples

First, these commit messages tell me nothing more than
the diff itself: stuff is being junked.  It would be interesting
to know why it is junked, why this does not remove any interesting
information, or where copies can be found.

We are junking things like

    -  texidoc = "The B\\\"arenreiter edition of the Cello Suites is the
    -most beautifully typeset piece of music in our collection of music (we
    -both own one. It is also lovely on French Horn). This piece does not
    -include articulation, but it does follows the same beaming and
    -linebreaking as the printed edition. This is done in order to
    -benchmark the quality of the LilyPond output.
    -As of lilypond 1.5.42, the spacing and beam quanting is almost
    -There are two tweaks in this file: a line-break was forced before
    -measure 25, we get back the linebreaking of Baerenreiter.  The stem
    -direction is forced in measure 24. The last beam of that measure is up
    -in Baerenreiter because of context. We don't detect that yet.
    -Note that the Barenreiter edition contains a few engraving
    -mistakes. The second line begins with measure 6 (but prints 5). The |:
    -half way in measure 13 has been forgotten.
    - "

are you sure you want to just junk these things?  I for one would
consider it a very bad regression if this baerenreiter sarabande
example would ever compile to something less beautiful than it
does now.

Of course, regression is the end of all tests.  However, after a major
hack, as a developer you would want to make sure that typography-demo
produces something worth-wile again.  Also, I think it always had the
feature of using all stencil backend functions, so you'd know during
a hack how far you are.  The sarabande has been a good smoke test for

If you meant to move some of these, it is /much/ nice to preserve
history, rather than copy or later re-introduce [ie, revert these
commits and do a move].

Also, I'm not sure why the totally obvious input/example-*.ly
had to go.  This seems to me as being such a nice-no-need-for-
documentation-nobrain place to get going?  After an install
on a new/foreign machine, I would do 

    lilypond /usr/share/doc/lilypond/input/

[and/or some other files from input/].  Why does this have
to change, and why did this happen without any mentioning
of what the new mantra is like?

Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
AvatarĀ®:    |

reply via email to

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