organization of input/

[Graham Percival]

I have a few questions about various subdirs of input/ and what they're
intended to do.

ascii-art: most of these files depend on "paper-as{5,9}.ly", but I can
only find "paper-as{5,6}-init.ly".  Is this dir a relic from ancient
times, or can Lilypond seriously produce ascii art (and just lost the
translation between paper-as5-init.ly and paper-as5.ly)?

mutopia: are these examples used in the manual for specific things, or
are they just included for general examples?  If they're just general
examples, then I suggest simply linking to Mutopia and letting people
browse through Mutopia, rather than including a few examples.  (I know
that the mutopia/ stuff has been there for a long time, and it made
sense to do it when mutopia only had a few files; but now that it has
270+ or so, we might as well point people to the real thing.)

sondag-morgen: is this an example, and if so, is it linked from the
manual, tutorial, or similar document?

test: on the web site, this is linked as "tips and tricks".  Might it
be a good idea to call the dir "tricks/" rather than "test/"?  (I know
it might be difficult to change the name in all the buildscripts; maybe
it isn't worth changing the name)

While I'm editing input/test, what should I do if I find a file that
doesn't demonstrate a trick (and instead appears to test some Lilypond
feature)?  Should I move it to input/regression?  Mark it for possible
deletion?
(for example, input/test/beams.ly -- it looks nice, but I don't think
anything in there is particularly `tricky' or demonstrates anything
particularily difficult)


In general, do we expect users to browse through input/ (or various
subsections of input/, such as input/test and input/mutopia), or do
expect users to only use the HTML files?  If we want to encourage
users to browse through input/test and input/mutopia without using
the HTML documentation, then might it be a good idea to move parts
of input/ into the Documentation/ tree?  Or perhaps rename "input"
to "examples"?

I know that when I was a newbie, I never thought to look in input/
for examples and tricks.  I know that we've added a link to
"input/test" under the "information for users" section, but as far
as I know, there's no similar links to input/mutopia and other
examples under the input/ tree.


Cheers,
- Graham